Configuring OAuth assertion grant contract fulfillment
Map values from the SAML assertions or JSON web tokens (JWTs) to the attributes defined for the attribute contract. The access token manager instance requires these values to create an OAuth access token.
About this task
At runtime, a single sign-on (SSO) operation fails if PingFederate cannot fulfill the required attribute.
Steps
-
On OAuth Assertion Grant Attribute Mapping > OAuth Assertion Grant Attribute Mapping Configuration > Contract Fulfillment , select a source from the Source list and then choose or enter a value for each attribute.
The following table describes the available mappings for each Source value:
| Source | Value | ||
|---|---|---|---|
Assertion |
When selected, the Value list populates with attributes from the SAML assertion or the JWT. For example, to map the value of |
||
Context |
When selected, the Value list populates with the available context of the transaction.
|
||
Extended Client Metadata |
Values are returned from the client record. |
||
LDAP, JDBC, or Other |
When selected, the Value list is populated with attributes that you have selected from the datastore. Select the desired attribute from the list. |
||
Expression |
When enabled, this option provides more complex mapping capabilities, such as transforming incoming values into different formats. Select Expression from the Source list, click Edit under Actions, and compose your OGNL expressions. All variables available for text entries are also available for expressions. For more information, see Text. Expressions aren’t enabled by default. Learn more about enabling and editing OGNL expressions in Attribute mapping expressions. |
||
No Mapping |
Select this option to ignore the Value field. |
||
Text |
When selected, the text you enter is used at runtime. You can mix text with references to any of the values from the SSO token, using the When applicable, you can enter values from your datastore using the
|
-
Click Next.