OIDC Scopes vs Claims

Follow
    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All

    Description:  

    How do OIDC Scopes relate to Claims

     

    Cause:  

    FAQ

     

    Resolution:  

    There is a direct relationship between scopes and claims.

    We follow the specs outlined here 

    For example:
    openid
    REQUIRED. 
    profile
    OPTIONAL. This scope gives the name, family_name, given_name, middle_name, nickname, preferred_username, profile, picture, website, gender, birthdate, zoneinfo, locale, and updated_at claim.
    email 
    OPTIONAL. This scope gives the email and email_verified Claims.
    address
    OPTIONAL. This scope gives requests access to the address Claim.
    phone
    OPTIONAL. This scope gives the phone_number and phone_number_verified claims. 

     

     

    Special Considerations:  

    On the PostAuth tab, be sure to map the required claims to a profile field otherwise they will still not be included in the ID Token. 

     

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.