Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Identity mapping

Updated on July 1, 2021

The Identity Mapping rule form allows you to specify how to identify an operator from a SAML 2.0 Assertion, JSON Web Token, or custom source.

When you register a user through OAuth 2.0 Client Registration, you can choose to authenticate the user with the attribute values that are provided in the SAML 2.0 Assertion or with claims that are provided in the JSON Web Token. To identify the operator, you can map the attributes from the SAML 2.0 Assertion or the claims from a JSON Web Token to the operator record in Pega Platform. You can also choose to use a custom source to identify the operator by providing password credentials as an operator.

The Identity Mapping data instance is referenced in the OAuth 2.0 Client Registration rule form.

  • Previous topic Creating an identity mapping data instance
  • Next topic Using JNDI to specify an LDAP server when using an authentication service

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us