OIDC Clients must be configured in the OIDC Provider in order to gain access to supported services. The provisioning process results in security credentials issued to the requesting party. The client must use these credentials to authenticate with REST API of the OIDC Provider.
| Environment | Client provisioning requests |
|---|---|
| PRE-PROD | Visit the OIDC preprod service desk to request provisioning of an OIDC Client for test in the pre-production environment. |
| PROD | Contact salg@bankidnorge.no to request provisioning of an OIDC Client in production. A valid contract with BankID Norge AS or one of its resellers is required for provisioning in production. |
| CURRENT | Visit the OIDC current service desk to request provisioning of an OIDC Client for test in the current environment. |
The following information must be supplied as part of the provisioning request:
| Item | What |
|---|---|
| 1 | Description of the OIDC Client and its intended use. |
| 2 | Contact information for both technical and commercial issues. |
| 3 | Requested OAuth2 flows |
| 4 | Requested Identity Providers. If BankID is requested, optionally a BankID Merchant certificate to be used, thus replacing the default certificate of the OIDC Service itself. |
| 5 | Requested Value Added Services (VASs). |
| 6 | One of more URLs where control will redirected back to the OIDC client (redirect URLs must be pre-registered for safety reasons). |
| 7 | A display name for the OIDC Client that will be shown in the header of the (default) OIDC dialogues. |
| 8 | Requested access to Norwegian National Identity Number. Note that such access will only be granted for eligible applications. |