Configure Ping Identity for SAML

Cisco Secure Access uses Security Assertion Markup Language (SAML) to authenticate and authorize web requests from user devices on networks and network tunnels with Web security enabled, and requests to private resources from user devices with Zero Trust (ZT) enabled. To support SAML authentication and authorization, you must configure the integration of an SAML identity Provider (IdP) in Secure Access.

Configure the Ping Identity SAML IdP with Secure Access by uploading the Ping Identity XML metadata file to Secure Access, or alternatively add the Ping Identity metadata in Secure Access manually.

Table of Contents

Prerequisites

For information on prerequisites that apply to all SAML IdPs, see Prerequisites for SAML Authentication.

Procedure

Step 1 – Choose an Authentication Method

  1. Navigate to Connect > Users and Groups and click Configuration Management.
  1. Navigate to SSO authentication and click Configure.
  1. For Authentication Method, choose Security Assertion Markup Language (SAML), and then click Next.

Step 2 – Add an Identity Provider

  1. For Identity Provider, choose PingID. Secure Access supports various IdPs.
  1. (Optional) Enable an organization-specific entity ID.
    • Organization-specific Entity ID—Choose this option when you have multiple Secure Access Orgs and need to configure SAML authentication for Secure Access Internet Security and Zero Trust (ZT) for these Orgs against the same IdP. The Secure Access SAML default common EntityID is saml.fg.id.sse.cisco.com. Secure Access allows you to override the default Secure Access SAML EntityID on a per-Org basis.
  2. For Entity ID URL, click Copy URL to make a local copy of the Secure Access Entity ID URL. The Secure Access SAML default common EntityID is saml.fg.id.sse.cisco.com.
  1. Choose a time interval when a user must authenticate with Secure Access, or select Never.
    The time intervals are:
    • Daily
    • Weekly
    • Monthly
  1. Click Next.

Step 3 – Add the Identity Provider's SAML Metadata to Secure Access

Download the Secure Access Metadata XML file and use the service provider file to configure your instance of Ping Identity. The Secure Access Metadata XML file includes the Secure Access root certificate.

Then, either upload the Ping Identity SAML metadata XML file to Secure Access or add the SAML metadata directly in Secure Access.

Step 3a – Upload the Identity Provider's SAML Metadata XML File

Download the Secure Access Metadata XML file, configure the SAML IdP, and then upload the IdP's metadata XML file to Secure Access.

  1. Check SAML Metadata XML Configuration.
  1. Click Download service provider XML file to save the Secure Access service provider XML metadata file to your local system.
    The Secure Access service provider (SP) metadata includes the service provider Issuer ID, the assertion consumer endpoint URL information, and the SAML request signing certificate from Secure Access. The Secure Access metadata is required when configuring your IdP.

    Your IdP must send the Cisco Secure Access User principal name in the NameID attribute in the SAML assertion. For more information on configuring your IdP, exporting your IdP metadata, obtaining your IdP details, or downloading your IdP's signing certificate, refer to your vendor's documentation.

  2. Configure Ping Identity for SAML.
    You must configure Secure Access as a generic SAML 2.0 application within Ping Identity. Ping Identity does not provide a method to upload Secure Access metadata for automatic configuration. Extract the EntityID and AssertionConsumerService URLs from the Secure Access metadata and add these to the applicable fields in Ping Identity. Contact Ping Identity for assistance.

  3. Upload the configured IdP Metadata XML file to Secure Access, and then click Done.
    The IdP's Metadata XML file contains the IdP's root certificate, which is required to integrate the IdP with Secure Access.

Step 3b – Add the Identity Provider's SAML Metadata

Note: If you uploaded your IdP's SAML Metadata XML file to Secure Access, you do not have to complete the following steps.

Download the Secure Access Metadata XML file, configure the SAML IdP, and then add the IdP's metadata in Secure Access.

  1. Check Manual Configuration.
  1. Click Download service provider XML file to save the Secure Access service provider XML metadata file to your local system.
    The Secure Access service provider (SP) metadata includes the service provider Issuer ID, the assertion consumer endpoint URL information, and the SAML request signing certificate from Secure Access. The Secure Access metadata is required when configuring your IdP.
    Your IdP must send the Cisco Secure Access User principal name in the NameID attribute in the SAML assertion. For more information on configuring your IdP, exporting your IdP metadata, obtaining your IdP details, or downloading your IdP signing certificate, refer to your vendor's documentation.

  2. Configure Ping Identity for SAML.
    You must configure Secure Access as a generic SAML 2.0 application within Ping Identity. Ping Identity does not provide a method to upload Secure Access metadata for automatic configuration. Extract the EntityID and AssertionConsumerService URLs from the Secure Access metadata and add these to the applicable fields in Ping Identity. Contact Ping Identity for assistance.

  3. Enter the identity provider's metadata, and then click Done.

    • Entity ID—A globally unique name for an identity provider.
    • Endpoint—The URL used to communicate with your identity provider.
    • Signing Keys—Your identity provider’s x.509 certificate that is used to sign the authentication request.
    • Signed Authentication Request (optional)—Choose whether you can sign the authentication request for the IdP.

Test the Identity Provider Integration

To complete the integration of the SAML IdP with Secure Access, evaluate the single sign-on authentication through the IdP. For more information, see Test SAML Identity Provider Integration.

View the SAML Certificates in Secure Access

Once you have completed the integration of an SAML IdP in Secure Access, you can manage the root certificates used in SAML authentication for Secure Access (service provider) and the SAML IdP. For more information, see Manage Certificates.


Configure Duo Security for SAML < Configure Ping Identity for SAML > Configure OpenAM for SAML