Guides
Secure Access Help Center

Configure Okta for SAML

Secure Access uses the 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 Access (ZTA) enabled.

To support SAML authentication and authorization, you must configure the integration of an SAML identity provider (IdP) in Secure Access. Configure Okta for SAML authentication with the Secure Access service provider metadata and then add your Okta SAML metadata to Secure Access.

For information about provisioning users from Okta to Secure Access, see Provision Users and Groups from Okta.

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

Step 2 – Add an Identity Provider

  1. For Identity Provider, choose Okta. 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 Network Access (ZTNA) 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, or Monthly.
  1. Click Next.

Step 3 – Configure the Identity Provider's SAML Metadata

Download the Secure Access metadata files and use the service provider file to configure your instance of Okta.

The Secure Access service provider metadata includes the service provider Issuer ID, the assertion consumer endpoint URL, 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.

Step 3a – Download the Secure Access Service Provider files

Note: Encrypted SAML assertions are a compliance standard in many industries and mitigate the risk of intercepted SAML assertions. For more information, see Prerequisites for SAML Authentication.

  1. Check SAML Metadata XML Configuration or Manual Configuration.
  2. Choose between unencrypted or encrypted SAML assertions.
    1. Click Download Service Provider XML file for the metadata XML file with the Secure Access root certificate that supports unencrypted SAML assertions.
    2. Click Download Zip file for the metadata XML file and signing and encryption certificate files required for encrypted SAML assertions. This metadata XML file includes the root certificate metadata for both the signing and the encryption certificates.
  1. Open the Cisco_SSE_SP_Metadata XML file.
  2. Copy the certificates from the Cisco_SSE_SP_Metadata XML file to a new file and save. Use the certificate file in the next step when you create the app integration in Okta.

Step 3b – Add Secure Access Service Provider Metadata to Okta

Add the Secure Access service provider metadata to your instance of Okta, then download the IdP metadata file to finish configuring Secure Access in the next step.

You must configure Secure Access as a generic SAML 2.0 application within Okta. Okta does not provide a method to upload Secure Access metadata for automatic configuration. Extract the EntityID and AssertionConsumerService values from the Secure Access metadata file and add these to the applicable fields in Okta.

Contact Okta for assistance. 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.

  1. Sign in to your instance of Okta, then navigate to Applications > Create a new app integration.

  1. Click SAML 2.0, and then click Next.
  2. For General Settings, add a name for the app integration, and then click Next.
  3. For SAML Settings > General, enter the values from the service provider metadata file that you downloaded in Step 3a – Download the Secure Access Service Provider XML File .
    • For Single sign-on URL, add the value of the Location attribute for the md:AssertionConsumerService element. The value should be something like: https://fg.id.sse.cisco.com/gw/auth/acs/response.
    • For Audience URI (SP Entity ID), add the value of the entityID element.
      The value should be something like: saml.fg.id.sse.cisco.com.
    • For Name ID format, choose EmailAddress.
  1. Click Show Advanced Settings.
  2. For Signature Certificate, upload the root certificate that you downloaded from the Cisco_SSE_SP_Metadata XML file. Click Preview the SAML Assertion to show the created metadata file, and then click Next.
  3. Click I'm an Okta customer adding an internal app, and then click Finish.

Step 3c – Add the Okta SAML Metadata to Secure Access

If you used SAML Metadata XML Configuration in step 3a above, upload your configured Okta SAML Metadata XML file to Secure Access, then click Done.

If you used Manual Configuration in Step 3a above, enter your Okta SAML metadata for the following Secure Access settings:

  • 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 to sign the authentication request for the IdP.

  1. On Okta, navigate to Sign on > Settings > Metadata details.


  2. On Okta, copy the value of Metadata URL. Navigate to Secure Access and and enter the value in Entity ID .

  3. On Okta, click More Details.

  4. On Okta, copy the value of Sign on URL. Navigate to Secure Access and enter the value in Endpoint.

  5. On Okta, copy the value of Signing Certificate. Navigate to Secure Access and enter the value in Signing Keys.

  6. (Optional) Navigate to Secure Access and choose whether to sign the authentication request.

  7. On Secure Access, click Done.

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 Microsoft Entra ID for SAML < Configure Okta for SAML > Configure AD FS for SAML

Updated about 1 month ago