OIDC SSO configuration
This document describes how to configure single sign-on (SSO) using the OpenID Connect (OIDC) protocol.
To learn about the SSO protocols supported in IDaaS, see Standard protocols.
OIDC grant types
You can select one or more of the following grant types:
Grant type | Description |
Client credentials client_credentials | The client credentials grant type allows an application to exchange its This grant type is enabled automatically when you enable APIs for the application, so you do not need to select it. |
Authorization code authorization_code | The authorization code is the most common grant type for OIDC applications in IDaaS. The application delegates the sign-in process to IDaaS and then parses the returned |
Refresh token refresh_token | This grant type allows an application to use a |
Device flow device | The device flow is for applications that lack a browser-server architecture. If a device cannot display the IDaaS sign-in page, this flow lets the user sign in from a browser on a separate device. |
For standard web-based enterprise applications, we recommend that you select the authorization code and refresh token grant types.
For applications without a browser-server architecture, we recommend that you select the device flow and refresh token grant types.
IDaaS does not currently support other OIDC grant types. If you require a different grant type, you can submit your request. Requests are evaluated and prioritized based on urgency and importance.
IDaaS configuration
| Parameter | Description | Example |
Basic Settings (required) | Grant types | Select the grant types that the application will use. | Select: Authorization Code Select: Refresh Token |
Redirect URIs | An allowlist of URIs where users can be redirected after authentication. When an application requests to sign in, the | http://www.xxxx/oidc/sso http://www.xxxx/oidc/sso2 | |
Authorization Scope | For more information, see SSO overview. | Select: All Users | |
Advanced Settings (optional) | Scopes scopes | Defines which user information the application can retrieve from the UserInfo Endpoint after a user signs in.
| Select: openid Select: email Select: profile |
PKCE | This option is available when the authorization code grant type is selected. If enabled, the authorization code flow uses the more secure Proof Key for Code Exchange (PKCE) extension. | Not selected by default. | |
Code validity period |
|
| |
Code challenge method | This option appears only when PKCE is enabled. It specifies the method used to generate the Code Challenge for the PKCE extension. | - | |
access_token validity period | The application uses the | 2 hours | |
id_token validity period | The | 10 hours | |
refresh_token validity period | Used to obtain a new | 30 days | |
Extended id_token fields | You can extend the Note Any fields added to the payload are publicly visible, so use this feature with caution. | - | |
id_token signing algorithm | Specifies the asymmetric algorithm for signing the | RSA-SHA256 | |
SSO Initiator | Specifies whether the application or the IDaaS portal initiates the SSO flow. | Application Only | |
IDaaS Sign-In URL | If you allow SSO to be initiated from both the portal and the application, you can enter a sign-in URL. This is the application URL where IDaaS should redirect users to start the SSO flow. Upon receiving the request, this URL must immediately redirect to the IDaaS /authorize endpoint. | - |
Application configuration
Using the OIDC protocol, applications authenticate by calling a standard set of endpoints provided by IDaaS.
The following table describes the available endpoints.
Parameter | Description | Example |
Issuer | A field in the | https://xxxxx.aliyunidaas.com/oidc1 |
Discovery Endpoint Discovery | Retrieves metadata about the OIDC configuration, such as endpoint locations and supported parameters. This endpoint is publicly accessible. | https://xxxxx.aliyunidaas.com/oidc1/.well-known/openid-configuration |
Authorization Endpoint Authorization | The endpoint where the application initiates the SSO flow by redirecting the user. | https://xxxxx.aliyunidaas.com/oidc/authorize |
Token Endpoint token | In the single sign-on (SSO) process, after the application obtains the authorization code | https://xxxxx.aliyunidaas.com/oidc/token |
JWKS endpoint JWKS | The JSON Web Key Set (JWKS) endpoint provides the public key for verifying the | https://xxxxx.aliyunidaas.com/oidc1/jwks |
UserInfo Endpoint Userinfo | After a user signs in, the application calls this endpoint with an | https://xxxxx.aliyunidaas.com/oidc1/userinfo |
End Session Endpoint SLO | Signs the user out of their main IDaaS session. | https://xxxxx.aliyunidaas.com/oidc1/logout |