Availability and access 1
 The following information must be supplied as part of the provisioning request: Â
No | What |
---|---|
1 | Description of the OIDC Client and it's intended use. |
2 | Contact information for both technical and commercial issues. |
3 | Requested OAuth2 flows (code, hybrid, implicit) |
4 | Requested client authentication method (only  |
5 | Requested Identity Providers (IDPs). If BankID is requested, optionally a BankID Merchant certificate to be used, thus replacing the default certificate of the OIDC Service itself. |
6 | Requested Value Added Services (VASs) |
7 | One of more URLs where control will redirected back to the OIDC client (redirect URLs must be pre-registered for safety reasons). |
8 | A display name for the OIDC Client that will be shown in the header of the (default) OIDC dialogues. |
9 | Requested access to Norwegian National Identity Number. Note that such access will only be granted for egligible applications. |
The provisioning process results in the return of a client_id
 and a client_secret
 that the OIDC Client must use to authenticate itself over the REST API for the OIDC Provider.