The scopes supported by an operator will be defined in the scopes_supported parameter of the Mobile Connect Provider Metadata or in the Discovery response links array.

Constructing scope values

All scope values MUST use the openid scope and one or more of the other scope values

e.g.

scope=openid address phone

Table of scopes

The following table list the scope values that may be available to use.

Scope Product Profile Description
openid Authenticate v1.1 By default, Mobile Connect authentication must be executed.
mc_authn Authenticate v2.0 As for openid but only supported from Mobile Connect Release 2 onwards.
mc_authz Authorise v2.0 OIDC scope to identity Mobile Connect Authorisation products.
mc_identity_signup Sign-up v2.0 Execute authentication and capture consent for sign up details.
mc_identity_phonenumber Phone Number v2.0 Execute authentication and capture consent for MC enabled phone number.
mc_identity_nationalid National ID v2.0 Execute authentication and capture consent for national ID.
profile * N/A v1.1 This requests that access to the End-User’s profile Claims excluding the address and email Claims at the UserInfo Endpoint be granted by the issued Access Token.
email * N/A v1.1 This requests that access to the email and verified Claims at the UserInfo Endpoint be granted by the issued Access Token.
address * N/A v1.1 This requests that access to address Claim at the UserInfo Endpoint be granted by the issued Access Token.
openid phone * N/A v1.1 This requests that access to the phone_number Claim at the UserInfo Endpoint be granted by the issued Access Token.
openid offline_access * N/A v1.1 This scope value requests that an OAuth 2.0 Refresh Token be issued that can be used to obtain an Access Token that grants access to the End-User's UserInfo Endpoint even when the End-User is not present (not logged in).

 

Scopes marked with * are not part of Mobile Connect but may be supported by some operators

Country specific scope values

Some countries support scope values which are specific to the country implementation. Details of these scopes can be found in the Country specific variations section.