An attribute contract is the set of user attributes that you and your partner have agreed will be sent in single sign-on (SSO) tokens for this connection.
You can extend the attribute contract with additional attributes. Optionally, you can configure PingFederate to mask individual extended attributes in its logs. For more information, see Attribute contracts and Attribute masking.
If you are creating or updating a SAML or an OpenID Connect identity provider (IdP) connection, consider using the partner's metadata to do so. If the metadata contains the required information, PingFederate automatically populates the attribute contract for you.
On the Attribute Contract tab, enter the attribute name in
the text box.
Attribute names are case-sensitive and must correspond to the attribute names expected by your partner.Tip:
If you are configuring a SAML connection to an InCommon participant, the assertion might contain attributes such as
urn:oid:220.127.116.11, which are standard names under various specifications, such as RFC4524 and RFC4519. For more information, see www.incommon.org/participants. The following table describes a subset of the object IDs (OIDs) referenced by the most common attributes used by InCommon participants.
OID value Description 0.9.2342.19200300.100.1.3 18.104.22.168.4.1.5922.214.171.124.1
For other attributes, see the metadata from your partner. The FriendlyName values, if available, should provide additional information about the attributes. Alternatively, third-party resources, such as www.ldap.com/ldap-oid-reference and www.oid-info.com, might help as well.
- Optional: Select the check box under Mask Values in Log.
- Click Add.
- Repeat until all desired attributes are defined.
Click Edit, Update, and Cancel to make or undo a change to an item. Click Delete and Undelete to remove an item or cancel the removal request.