다큐멘트 센터 IAM User Guide Example of Using Azure for OIDC SSO

Example of Using Azure for OIDC SSO

최신 업데이트:2026-03-25 15:16:56

Operation Steps

1. Log in to the Azure platform and locate Microsoft Entra ID

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

2. In App registrations, create a new application by clicking New registration

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

3. Complete the application information, select web as the redirect address type, and enter the redirect URL

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

Redirect URL: https://login.cdnetworks.com/cas/login?client_name=
Modify this based on the configuration in the console from the previous steps.
For example, if you set the IdP Name to test, enter the following: https://login.cdnetworks.com/cas/login?client_name=test

4 Open the console, go to [Access Control] -> [Identity Provider], and add a new identity provider configuration.

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明
Fill in the same [Provider Name] on the console as the IdP Name set in step 3, and select Azure as the [OIDC Type].
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

5. Enter the Client ID and Tenant ID into the respective fields in the Config Form on the console, as shown in the diagram.

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

6. Set a password for the application. Navigate to the Certificates & secrets section, and click New client secret to add a password.

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

Then enter the password’s Value field into the Config Form on the console, as shown in the diagram.
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

7. To assign application access permissions to users, return to the Overview page and click ‘Go to Enterprise applications’.

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明
Go to ‘Users and groups’, add users, and select the users or user groups that need authorization from the existing users or user groups.
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明
Select user
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

8. Finally, return to the console and fill in both the [Identity Provider URL] and [User Mapping Field] information.

关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

(Identity Provider URL) The fixed format is:
https://login.microsoftonline.com//v2.0/.well-known/openid-configuration
Here, needs to be replaced with the Tenant ID value from Step 5.

(User Mapping Field) Optional values: name, email
If the content entered is name, please verify the user information on the Azure platform to ensure that the value of the Display name matches the login account on the console.
If the content entered is email, please verify the user information on the Azure platform to ensure that the value of Email matches the login account on the console.
关于 HTTP/2 Bomb 漏洞(CVE-2026-49975)的风险说明

이 문서의 내용이 도움이 되었습니까?
아니오
정상적으로 제출되었습니다.피드백을 주셔서 감사합니다.앞으로도 개선을 위해 노력하겠습니다.