- A scope is a way for the OIDC Client to indicate to the OIDC Provider what service it requests access to, or in technical terms which resources at pertinent Resource Servers. The response from a Resource Server consists of datasets with attributes on the user and/or the authentication event.
- Members of such a dataset are referred to as claims.
A Scope in OIDC can, therefore, be thought of as a shorthand for a larger pre-defined bundle of Claims. An OIDC Client may also request individual Claims, or any set of Claims, for fine-grained access.
The set of Claims returned to an OIDC Client in a response from the OIDC Provider may differ from the set of Claims that were requested. First, because an OIDC Client may not be eligible to the full set of claims that are supported by the BankID OIDC Provider. Second, because the end-user is always in control via consent handling.
The content of the ID Token that is returned in response to a successful authentication (or session refresh) is governed by the standard scopes
profile. These scopes are available to any OIDC Client. Some additional content is governed by custom scopes defined by the OIDC Provider from BankID, among them the Norwegian National Identity Number (
nnin) that can be made available to eligible OIDC Clients. See the description of ID Tokens for further information.
Scopes and claims beyond those associated with ID Tokens are used to request Access Tokens (with corresponding Refresh Tokens) of the right kind for subsequent access to various resources at supported resource servers.
Supported scopes in the BankID OIDC Provider
Below we've listed all scopes supported by the BankID OIDC Provider. Note that
- Some scopes will result in ID Token claims (once the authorization code is exchanged for tokens)
- Some scopes will result in additional tokens in token response, i.e. bankid_proof.
- Some scopes will result in a
resource_accesspart in the Access Token (once the authorization code is exchanged for tokens). This is needed when downloading the actual results (claims) from the designated resource servers, using this Access token as a bearer token.
- Some scopes will result in specific flows, i.e. sign, chgpwd.
|Used to get the minimum part of the ID Token. Can be used to authenticate users in an anonymous way.||authorize||Claims in ID Token|
|Used to enrich the ID Token with the end user's name and birthdate. Does not involve end user consent.||authorize||Claims in ID Token|
Used to enrich the ID Token with end user's national identity number. Does not involve end user consent.
|Used to retrieve proof of BankId Netcentric or BankID on Mobile authentication by including end user signature, OSCP response and information used to generate message digest signed by end-user.||authorize||See BankID Proof for more information.|
|chgpwd||Used to initiate an enduser change of password in the BankID WebClient.||authorize||no additional claims|
The end user is prompted for a new password in the BankID Webclient after successfully authentication using the old password.
Used for creating and uploading a signing order to the SignDoc resource server through client credential grant.
|Used when initiating a signing transaction||authorize||Claims are downloaded through signdoc or signdoc/pades, depending on the solution|
Used to request access to end user's national identity number. This will prompt end user consent for sharing their data.
Used to request access to end user's address. This will prompt end user consent for sharing their data.
Used to request access to end user's phone number. This will prompt end user consent for sharing their data.
Used to request access to end user's email address. This will prompt end user consent for sharing their data.