- On the Back-Channel Authentication screen, click Configure to the right of the list of messages under Received from your partner.
On the Inbound Authentication Type screen, choose one or
more authentication methods.
- HTTP Basic
- When selected, the administrative console prompts you to enter the credentials
on the Basic SOAP Authentication (Inbound) screen.Important:
If you are configuring more than one connection that uses the artifact or HTTP profile, you must ensure that the username is unique for each connection.
- You must communicate these credentials to your partner out-of-band.
- SSL Client Certificate
- When selected, the administrative console prompts you to specify the trust model and the related certificate settings on subsequent screens (see next step).
- Digital Signature (Browser SSO profile only)
- You select a signing certificate on a subsequent screen, Signature Verification Settings.
- This option leverages on the digital signature of the message.
- Require SSL
- When selected, incoming HTTP transmissions must use a secure channel. This option is selected by default.
- You may clear the check box if you do not require a secure channel and client certificate authentication.
For SAML 2.0, use these options in any combination or independently. For SAML 1.x, you must enable HTTP Basic authentication, client certificate authentication, or both; you may also add digital signing to ensure message integrity.
If you chose SSL Client Certificate in the previous
step, select a trust model on the Certificate Verification
- The partner certificate must be signed by a trusted certificate authority (CA). Optionally, you may also restrict the issuer to a specific Trusted CA to mitigate potential man-in-the-middle attacks and to provide a means to isolate certificates used by different connections. The CA's certificate must be imported into the PingFederate Trusted CA store on the screen.
- The partner certificate is self-signed or you want to trust a specified certificate.
When anchored certificates are used between partners, certificates may be changed without sending the update to your partner. If the certificate is unanchored, any changes must be promulgated.
(For more information, see Digital signing policy coordination.)
Trust model Subsequent steps Anchored On the Subject DN screen:
- Enter the Subject DN of the certificate.
- (Optional) Select the Restrict Issuer check
box and enter the Issuer DN of the
Consider enabling this option to mitigate potential man-in-the-middle attacks and to provide a means to isolate certificates used by different connections.
Unanchored On the SSL Verification Certificate screen, select the client certification from your partner.
If you have not yet imported the client certificate from your partner, click Manage Certificates to do so (see Managing certificates from partners).
On the Summary screen, review your configuration and
perform one of the following tasks:
- Amend your configuration
- Click the corresponding screen title and then follow the configuration wizard to complete the task.
- Keep your changes
- Click Done and continue with the rest of the
When editing an existing configuration, you may also click Save as soon as the administrative console offers the opportunity to do so.
- Discard your changes
- Click Cancel.
Page created: 12 Sep 2019 |
Page updated: 19 Mar 2020