---
title: Interpreting Platform Single Sign-on authorization scopes
framework: authenticationservices
role: article
role_heading: Article
path: authenticationservices/interpreting-platform-single-sign-on-authorization-scopes
---

# Interpreting Platform Single Sign-on authorization scopes

Use authorization scopes to apply authentication policies.

## Overview

Overview When Platform Single Sign-on (Platform SSO) requests tokens from your identity provider, it can include the authorization scope in the request. The scope tells you why the user is authenticating, so you can apply the correct policy. For example, you can require multifactor authentication at login but not at screen unlock. Request authorization scopes To receive authorization scopes when Platform SSO sends a login or key request, set includePlatformSSOAuthorizationScopes to true in your ASAuthorizationProviderExtensionLoginConfiguration. Platform SSO sends those scopes to your keyEndpointURL and tokenEndpointURL. For web-based authentication, Platform SSO sends the scopes to the authorizationURL when you use a static OAuth URL. When you use a dynamic OAuth URL, Platform SSO sends the scopes to the authorizationURL that a pre-authentication request returns. For more information on the login request and web-based authentication, see Creating and validating a login request and Implementing web-based authentication with Platform Single Sign-on. Receive authorization scopes All authorization scopes that Platform SSO provides use the prefix urn:apple:platformsso:auth::  |   |   |   |   |   |   |   |   |   |   |  note: Platform SSO adds exactly one of these scopes per request. The scopes are mutually exclusive based on the originating user action. For most session-driven flows, Platform SSO selects the scope from the session type:  |   |   |   |   |   |   |  A few scopes fall outside the session-type mapping: Platform SSO applies the special-purpose scopes (create-user, temporary-session, fallback, and refresh) based on the specific feature path instead of the session type. When Platform SSO has no specific context, it uses login as the default. Treat login as the safe baseline and reserve stricter policy for the more specific scopes. For fallback, Platform SSO sends the same scope on both legs of the OpenID handshake — the initial authorization request and the subsequent token verification. Sending the same scope lets your identity provider apply policy decisions consistently across both requests.

## See Also

### Configuration

- [Configuring authentication with the identity provider (IdP)](authenticationservices/configuring-authentication-with-the-identity-provider-idp.md)
- [ASAuthorizationProviderExtensionLoginConfiguration](authenticationservices/asauthorizationproviderextensionloginconfiguration.md)
- [ASAuthorizationProviderExtensionLoginManager](authenticationservices/asauthorizationproviderextensionloginmanager.md)
