Tchater maintenant avec le support

Obtenir une aide instantanée
Terminer l’enregistrement

Se connecter

Demander les tarifs

Contacter le service des ventes

Cloud Access Manager 8.1.2 - How To Develop OpenID Connect Apps

Parcourir le contenu

Dell™ One Identity Cloud Access Manager 8.1.2 - How to Develop OpenID Connect Apps What is OAuth v2.0?

OAuth v2.0 flows

Authorization Code Flow Implicit Flow Approval OAuth v2.0 client types

public confidential

What is OpenID® Connect?

OpenID® Connect ID Token

iss sub aud exp iat auth_time nonce acr amr azp

OpenID® Connect Token signing OAuth v2.0 and OpenID® Connect response types Obtaining claims from Cloud Access Manager OpenID® Connect discovery When would you use OAuth v2.0 and OpenID® Connect? Using the OpenID® Connect Flow Test Tool

Client machine Cloud Access Manager administration Exchanging set up information between Cloud Access Manager and client machine Cloud Access Manager administration Client machine

Building your OpenID® Connect client Example: Providing OpenID® Connect SSO to a Salesforce.com Auth Provider

azp

OpenID® Connect Token signing

OpenID Connect requires that the ID Token must be digitally signed. Dell™ One Identity Cloud Access Manager offers two ways to sign the ID Token. You can sign the ID Token:

•

Using HMAC SHA-256 with an automatically-generated pseudo-random shared secret

•

Using RSA SHA-1 with a private key from a self-signed X.509 certificate

OAuth v2.0 and OpenID® Connect response types

Dell™ One Identity Cloud Access Manager supports the following response types:

Table 3. Supported response types

Response_type	Meaning	Comments
code	OAuth v2.0 authorization code flow
token	OAuth v2.0 implicit flow	Not used by OpenID Connect (no ID token returned)
id_token	OpenID Connect implicit flow	No access token returned. Claims are included in the ID Token
token id_token	OpenID Connect implicit flow	Claims are accessed by invoking UserInfo endpoint

Obtaining claims from Cloud Access Manager

Dell™ One Identity Cloud Access Manager does not use the scope values contained in the authentication request to determine what claims are to be returned. Instead, it returns the claims defined by the application configuration’s claim mappings. Thus the client cannot control what claims are returned to it.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation

© 2025 One Identity LLC. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center