Configuring a producer system for remote case types
To pass remote case types to another application, configure the system that stores your case types as a producer system. As a result, you provide a framework for case workers to process work from multiple applications without changing context, which promotes efficiency and saves time in your organization.
For example, your system might host Loan requests and Credit card operations applications. You want to publish case types from these applications to a VIP customers operations application so that users can perform work by logging in to this application only. You configure the system with the Loan requests and Credit card operations applications as the producer system first.Preparing OAuth 2.0 client registration for remote case types
To ensure that remote application from a consumer system can properly communicate with your producer system, prepare the OAuth 2.0 client registration in your producer system. As a result, you create a secure and reliable connection between your producer and consumer systems.
- In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click OAuth 2.0 Client Registration.
- In the list of instances, open the Remotecasetype_Producer OAuth 2.0 client registration.
- In the form header, click .
- On the Save OAuth 2.0 Client Registration As form, in the Client Name field, enter a unique label, and then click Create and open.
- In the form header, in the RS section, click
Edit, and then, in the text field, provide the
ruleset to associate with your application.
For example: Associating a rule with a ruleset - In the Client Credentials section, download the client ID
and client secret by clicking View & download, and
then click Save.
Note: You provide the client ID and client secret credentials when you register a remote system during creation of a remote case type. Ensure that you store the credentials safely.
Preparing a token profile for remote case types
After you prepare the OAuth 2.0 client registration for your remote case types, prepare a token profile. Token profiles secure data exchange between two parties, such as producer and consumer systems.
- In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click Token Profile.
- In the list of instances, open the Remotecasetype_Producer token profile.
- In the form header, click .
- On the Save Token Profile As form, in the
Name field, provide a unique label, and then click
Create and open.
For example: The following figure shows a sample new label for a token profile: Copying a token profie Note: Make note of the token profile name as this name is required during preparing identity mapping. - In the form header, in the RS section, click Edit, and then, in the text field, provide the ruleset to associate with your application.
- In the Claims mapping section, click Add a row.
- In the Claim name field, enter sub, and then, in the Property field, enter pxRequestor.pyUserIdentifier.
- In the Claims mapping section, click Add a row.
- In the Claim name field, enter
exp, and then, in the Property
field, enter OperatorID.pyExpirationDate.
Result: The following figure shows a correct configuration of the claims mapping: Claims mapping for the producer system - Click Save.
Preparing identity mapping for remote case types
After you prepare the client registration and token profile for your producer system, prepare identity mapping to ensure that Pega server correctly identifies operators in your application. You also define how to map the user identity information for use in the Pega application.
- In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click Identity Mapping.
- In the list of instances, open the Remotecasetype_Producer identity mapping.
- In the form header, click .
- On the Save Identity Mapping As form, in the Name field, enter a unique label, and then click Create and open.
- In the form header, in the RS section, click Edit, and then, in the text field, provide the ruleset to associate with the identity mapping.
- In the Token validation section, in the Token
processing profile field, enter the name of the token profile
that you created for the producer system, as in the following example:
For example: Token profile for identity mapping - Click Save.
Mapping the truststore to the token profile for remote case types
After you prepare the identity mapping, map the token profile to the truststore to ensure a secure encryption of data between your producer and consumer systems.

- In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click Token Profile.
- In the list of instances, open the token profile that you created for your
producer system.For more information, see Preparing a token profile for remote case types.
- In the Security section, in the Truststore field, enter the truststore that you created for the producer system.
- Click Save.
Mapping the identity mapping to the client registration for remote case types
Ensure that the producer and consumer system can communicate correctly and securely by mapping the identity mapping to the client registration that you created for the producer system.
- In the navigation pane of Dev Studio, click Records.
- Expand the Security category, and then click OAuth 2.0 Client Registration.
- In the list of instances, open the OAuth 2.0 client registration that you
created for the producer system.For more information, see Preparing OAuth 2.0 client registration for remote case types.
- In the Supported grant types section, in the
Identity mapping field, enter the identity mapping
that you created for the producer system.For more information, see Preparing identity mapping for remote case types.
- Click Save.
Previous topic Establishing trust between applications for remote case types Next topic Configuring a consumer system for remote case types