Configuring authentication request signing in PingOne for Enterprise

Configuring authentication request signing in PingOne for Enterprise - PingOne for Enterprise

Use Cases

bundle

solution-guides

ft:publication_title

Use Cases

Product_Version_ce

category

ContentType

howtodoc

ContentType_ce

How-to

For service provider (SP)-initiated single sign-on (SSO), your identity provider (IdP) or company policy might require signing the SAML authentication request.

Ensure that you have internet access.
If you do not already have a PingOne for Enterprise account, create an account.

Sign in to the PingOne for Enterprise admin portal.
Click Setup.
Click the Pencil icon.
Select PingFederate. Click Next.
If PingFederate is already installed:
1. Click Yes, then click Next.
2. Copy the provided activation key into PingFederate Bridge when prompted.
If PingFederate is not installed:
1. Click No, then click Next.
2. Click the appropriate server platform.
3. Download and install PingFederate Bridge, then click Next.
4. Copy the provided activation key into PingFederate Bridge when prompted.
If PingOne for Enterprise is configured with PingFederate version 8.0 or later, no changes in PingOne for Enterprise are necessary.

Note: If PingFederate is set to Require AuthN Requests To be Signed When Received via The Post or Redirect Bindings, PingOne for Enterprise automatically signs the authentication request.
If PingOne for Enterprise is configured with custom SAML:
1. Select the Sign AuthnRequest From PingOne check box. Click Next.
2. Click Manually Enter Your IDP Connection Information. Click Save.

PingOne for Enterprise will sign authentication requests during the SP-initiated SSO process. The verification certificate is inside the PingOne for Enterprise metadata file, and gets loaded into the SAML product when the metadata is uploaded for configuration.