Configure the CoreBlox IdP Adapter to determine how PingFederate communicates with the CoreBlox Token Service.
You can configure the adapter to direct authentication requests, authorization consent requests, or both to your application.
In the PingFederate
administrative console, create a new IdP adapter instance:
- For PingFederate 10.1 or later: go to . Click Create New Instance.
- For PingFederate 10.0 or earlier: go to . Click Create New Instance.
On the Type tab, set the basic adapter instance
- In the Instance Name field, enter a name for the adapter instance.
- In the Instance ID field, enter a unique identifier for the adapter instance.
- In the Type list, select CoreBlox IdP Adapter. Click Next.
- On the IdP Adapter tab, configure the adapter instance by referring to CoreBlox IdP Adapter settings reference. Click Next.
On the Extended Contract screen, add any attributes that you
want to include in the assertion. Click Next.
The CoreBlox Token Service returns a
userAttributeskey that lists a set of attributes. You can use any of these attributes to extend the attribute contract.
You can also include the
tokenkey in the extended attribute contract.
- On the Adapter Attributes tab, set pseudonym and masking options as shown in Set pseudonym and masking options in the PingFederate documentation. Click Next.
- On the Adapter Contract Mapping tab, configure the contract fulfillment details for the adapter as shown in Define the IdP adapter contract in the PingFederate documentation. Click Next.
On the Summary tab, check and save your configuration:
- For PingFederate 10.1 or later: click Save.
- For PingFederate 10.0 or earlier: click Done. On the Manage IdP Adapter Instances tab, click Save.
- Create an SP connection using this CoreBlox IdP Adapter instance. See Identity provider SSO configuration in the PingFederate documentation.