Skip to main content

Preparing a token profile for remote case types

Suggest edit Updated on November 26, 2021

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.

  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the Security category, and then click Token Profile.
  3. In the list of instances, open the Remotecasetype_Producer token profile.
  4. In the form header, click SaveSave as.
  5. 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
    A token profile Save As form with a new label provided
    Note: Make note of the token profile name as this name is required during preparing identity mapping.
  6. In the form header, in the RS section, click Edit, and then, in the text field, provide the ruleset to associate with your application.
  7. In the Claims mapping section, click Add a row.
  8. In the Claim name field, enter sub, and then, in the Property field, enter pxRequestor.pyUserIdentifier.
  9. In the Claims mapping section, click Add a row.
  10. 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
    The Claim mappings section of the Token Profile rule form
                                configured for the producer system
  11. Click Save.
    • Previous topic Preparing OAuth 2.0 client registration for remote case types
    • Next topic Preparing identity mapping for remote case types
    Did you find this content helpful? YesNo

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us