The OpenID Connect Provider from BankID (hereafter referred to as the BankID OIDC Provider) consists of an industry-standard interface to various identity-related services.
- See the problems we solve for further information on the products, features and functions of such services
- See how to get started for a high-level perspective on what's needed to go live
- See the technical documentation on provisioning for access, and how to integrate with such services via the REST API
- See the Release Notes for information on services supported in this particular release of the BankID OIDC Provider.
The term OIDC Client is used for any application that integrates with the OIDC Provider, corresponding to the following terms in related vocabularies:
- OAuth2 clients in OAuth vocabulary
- Relying Party in OIDC vocabulary
- Merchant in BankID vocabulary
OIDC Clients use Scopes and Claims to request access to services. Identity Providers return ID Tokens containing assertions about the end-user and (optionally) Access Tokens to gain subsequent access to resource servers for downloading signign results or end-user data through userinfo. Consent handling is a key feature of the OIDC Provider that puts the end-user in control of delegating rights to an OIDC Client to access any end-user data on behalf of the end-user.
Testing tools are available to test and get familiar with the OIDC Provider and its supported services. Developers may visit Vipps AS GitHub for source code examples.
Logg inn med Vipps
BankID is part of Vipps AS. Vipps AS also offers "Logg inn med Vipps" based on the OIDC standard. The service is a substitute for usernames and passwords providing zero- and one-click user experiences for applications that do not require the high security level offered by BankID. More information about the service can be found here: https://www.vipps.no/produkter-og-tjenester/bedrift/innlogging-og-identifisering/logg-inn-med-vipps/ with more technical documentation here: https://github.com/vippsas/vipps-login-api