The OIDC Provider from BankID supports authentication via the following set of IDPs. More IDP options may be added in the future. The last column shows if xID can be used in front of the IDP to derive any user ID that the IDP may depend on, thus simplifying user-experience.
|BankID on mobile||BIM||4||(Depends on TINFO)|
Each IDP option is associated with a Name and Level of Assurance (LoA) codified via attributes called
amr (Authentication Method Reference) and
acr (Authentication Context Class Reference). These attributes can be included in the request from an ODIC Client to the Authorize endpoint at the OIDC Provider to request either a particular IDP (
amr) or any IDP at a particular LoA (
acr). A standard and designated request parameter exists for the
acr attribute. Since there is no corresponding standard and designated parameter for the
amr attribute, the OIDC Provider from BankID supports
amr values codified as part of the
Sucessful authentication via one of the supported IDPs results in an ID Token being returned to the reqesting OIDC Client. The ODIC platform from BankID provides ID Tokens with uniform characteristics regarless of the IDP being used in any particular case.
Note that an ID Token also contain values for the
acr attributes, corresponding to the IDP actually being used. These values may be different from corresponding values provided in the request from the OIDC Client to the Authorize endpoint. One example is if more IDP options meet the
acr criteria of the Authorize request. In this case an IDP selector dialog is presented for the user to resolve which IDP to use. Another example is when xID performs a step-up to BankID.
See further details of separate pages for each of the supported IDPs how each IDP can be governed via
login_hint or JS Connectors.