The BankID IDP consists of the following options, distingused by Name, but both being LoA4 Services.
The BankID IDP in the OIDC Provider is a multi-tennant service having the capability to host several BankID merchant certificates. In its default configuration all OIDC Clients share a common BankID merchant certificate associated with the BankID OIDC Service itself. Alterntively, an OIDC Client may be configured with its own BankID merchant certificate. The BankID IDP supports each of the BankID B2C Services (includes support for both Bank netcentric and BankID on mobile).
| Warning | |
|---|---|
| Note | BankID via the OIDC Provider is currently restricted to authentication. Future support for BankID signing may be added. |
...
- The integration interface is the same for each of the BankID B2C Services (both BankID netcentric and BankID on mobile).
- The merchant does not need to implement any GUI for BankID on mobile since it is taken care of by the OIDC Provider itself
- The merchant does not need to implement a selector dialog for netcentric vs. mobil since the OIDC Provider offers such a selector dialogue.
- The integration interface is based on an industry-standard REST API being much more convenient than implementing via the legacy BankID-server.
- The merchant may have access to Supplementary Value Added Services (VAS) that are not available via the legacy BankID server.
An OpenID OIDC Client make use of BankID either via login hints directly in the authorize request of the REST API or via integration with the BankID the JS Connector.
An OIDC Client may also customize its use of the BankID IDP.