This is a list of the active deprecation warnings in BankID OIDC along with end of life dates.
Please review this list regularly to ensure your systems are up to date in order to avoid any service interruptions.
Removal of implicit flow support
End of Life: Q1 - 2024 (TBA)
We are completely removing support for implicit flow in our platform. This feature has long been discouraged and always been a restricted (R10) feature in BankID OIDC.
Removal of realm_access in access tokens
End of Life: Q3 - 2023 (TBA)
We are cleaning up usage of Realm Roles in our platform which impacts the realm_access claims in Access Tokens. From now on only resource_access claim is relevant for roles assigned to a user.
This change is mostly relevant to resource servers and not applicable for most merchants.
Removal of jwks_uri_enc and encryption of login_hint
End of Life: Q3 - 2023 (TBA)
The BankID OIDC proprietary encryption of the login_hint is replaced with the OIDC standard encryption of a request object.
BankID OIDC supports encrypted request object parameter in the authorization request. BankID OIDC also supports encrypted login_hint as an authorization request query parameter.
Instead of encrypting the login_hint using keys from the jwks_uri_enc endpoint, the login_hint should be added as a cleartext parameter to the request object and the request objectshould be encrypted using keys from the jwks_uri endpoint.
Token claim session_state is being replaced by sid
End of Life: Q2 - 2022 (TBA)
Today, all tokens will have both sid and session_state claims representing the same value (GUID related to session handling).
session_state will soon be removed from all tokens so make sure you do not depend on this claim. Use sid claim if you depend on this value.
Iframe is not recommended
End of Life: TBA
Inclusion of BankID OpenID Connect service in an iframe is not a recommended practice for integrating BankID.
In an effort to minimize attack vectors for phishing and clickjacking attacks and the situational blocking of third party cookies in major browsers wehave decided to not recommend using iframe on the BankID OIDC platform.
End-users can easily verify that they are on a legit BankID OIDC merchant by verifying the domain in the address bar.
End-users meet the BankID OIDC client through a standardized BankID OIDC user interface.
BankID OIDC wish to follow best industry practice that states that end-users should not be encouraged to authenticate through embedded forms (i.e. iframe and web-views).
Third-party cookies are required when using BankID OIDC via iframe. Browser vendors have worked actively to stop tracking of end-users across domains. This causes technical difficulties and bad end-user experiences.
When using iframe, there are a bigger risk that intruders can hijack the client via external scripts or browser plugins and thus phish information, change links or track the end-user.
What alternative integration modes are available?
Alternative integration modes are available to replace iframe, respectively window and redirect mode. In redirect mode, the browser redirects the user to our domain. In window mode, the browser opens a new window to our domain.
How can I customize the user interface for BankID OIDC?
Merchants can provide a name and a logo that is displayed when the client is loaded in window or redirect mode. The logo must have dimensions 150x30 px, file format PNG and a maximum file size of 10 kB. The logo can be sent to Vipps through our customer portal by creating a new issue, and then uploading the logo as an attachment on a comment after the issue has been created.
This notice is only relevant for BankID OIDC. We encourage our partners that use BankID server to consider alternative integration modes for their solutions, but there is no plans to deprecate iframe on BankID Server.