SDG

Configuring the IdP token processor

This section describes how to configure the SDG CTS Token Processor.

Steps

  1. In the PingFederate admin console, go to IdP Configuration > Token Processors.

    If you don’t see Token Processors on the main menu, enable WS-Trust under Server Settings on the Roles and Protocols screen by selecting WS-Trust for the IdP role.

  2. On the Manage Token Processor Instances page, click Create New Instance.

  3. On the Type tab:

    1. In the Instance Name field, enter a name of your choice for the token processor instance.

    2. In the Instance ID field, enter a unique identifier for the token processor instance.

      The Instance ID is used internally. It can’t contain any spaces or non-alphanumeric characters, and it must be uniquely named.

  4. In the Type list, select CoreBlox Token Processor. Click Next.

  5. On the Instance Configuration page, complete the following fields:

    Standard fields
    Field Description

    SDG Conversion Token Service URL

    The base URL for SDG Conversion Token Service (CTS).

    This field is blank by default.

    Validate SDG Conversion Token Service Certificate Hostname

    The hostname of the server certificate presented by the SDG Conversion Token Service must match the hostname in the SDG Conversion Token Service URL field.

    This checkbox is cleared by default.

    Client Certificate

    The certificate used for authentication calls to the CTS.

    SDG Conversion Token Service Tokentype

    The token type that the SDG Conversion Token Service is configured to provide to the adapter.

    The default and only allowed value is SMSESSION.

  6. (Optional) Click Show Advanced Fields to specify the token processor’s authorization configuration settings.

    Advanced fields
    Field Description

    Perform Authorize Request

    If selected, the token processor makes an authorize request to the CTS before accessing the protected resource.

    The following three fields are required for the adapter to make the authorize request.

    Resource

    The resource that the agent protects.

    Instance

    Refers to the name of the agent instance.

    Action

    The action to take when evaluating requests against the policy server.

  7. Click Next.

  8. (Optional) On the Extended Contract tab, configure additional attributes for the adapter.

    Learn more about key concepts in the Administrator’s reference guide in the PingFederate documentation.

  9. Click Next.

  10. On the Token Attributes page, select the Pseudonym checkbox for the userId attribute.

    You can also select this checkbox for any extended attributes specified on the Extended Contract tab.

    Learn more in Setting pseudonym and masking options in the PingFederate documentation.

  11. Click Next.

  12. On the Summary tab, verify that everything is correct, then click Done.

  13. On the Manage Token Processor Instances page, click Save to complete the token generator configuration.