CDNetworks Documentation IAM User Guide Example of Using Okta for SAML SSO

Example of Using Okta for SAML SSO

Last update:2026-03-25 15:22:03

Okta SAML Integration Steps

Log in to OKTA to configure the application

  1. Log in to the Okta platform as an administrator. In the upper right corner, click “Your Org” or [Admin].
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)

  2. Select “Applications” - “Applications” - “Create App Integration” to create an application.
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)

  3. Select the application type “SAML2.0” and click “Next” to enter the configuration page.
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    (1) Fill in the General Settings. Please configure as follows:
    App name: Application name;
    App logo (optional): Application logo identifier;
    App visibility: Select “Do not display application icon to users”
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    (2) Click “Next” and complete the Configure SAML section as follows:
    Single sign-on URL:
    https://login.cdnetworks.com/cas/login?client_name=${provider}
    Reference for provider creation: SAML Configuration for CDNetworks SP during SSO
    (3) Select “Use this for Recipient URL and Destination URL”;
    (4) Audience URI (SP Entity ID) configuration: https://login.cdnetworks.com
    (5) application username: Okta username
    (6) Show Advanced Settings configuration:
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    SAML Issuer ID: customizable. If left blank, a default value will be automatically generated.
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Reference documentation: SSO SAML Response
    (7) Click “Next”, select the appropriate option based on your actual business scenario, and then click “Finish”.
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    (8) Assignments (User Assignment)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)

Provider Information Configuration in CDNetworks Console

  1. View Okta metadata documentation
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
  2. Upload the metadata file to the CDNetworks Console
    Reference document: SAML Configuration for SP
    Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)

Access Test

  1. CDNetworks redirects to Okta authentication
    Access the address https://login.cdnetworks.com/cas/clientredirect?client_name=${provider} directly in your browser to verify whether it redirects to the Okta login page.
  2. Okta redirects to CDNetworks for authentication
    After Okta authentication is successful, it will redirect to CDNetworks for Single Sign-On without requiring username and password input.

Frequently Asked Questions

1. Issue: Login authentication failed, displaying the following message
Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
Solution:
Preview SAML information
Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
Confirm whether the value of Issuer is consistent with the entityID in the metadata file uploaded to CDNetworks Console.
Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
Response to OpenJDK Base64 Decoder Memory Corruption Vulnerability (CVE-2026-114938 / Java4Shell)
If inconsistencies are found, repeat the steps in part two. Download the latest configuration and re-upload it.

For other common issues, please refer to the documentation: FAQs about IDP Configuration

Is the content of this document helpful to you?
Yes
I have suggestion
Submitted successfully! Thank you very much for your feedback, we will continue to strive to do better!