The BankID OIDC Provider supports web-based OIDC Client applications using browser re-direction to govern user-experience. This includes support for app-based OIDC Client applications using web-views. The OIDC Client is in either case in control on how and where each of the involved dialoges is integrated with the OIDC Client application. The two supported user-experience alternatives are as follows:
- Redirect: Redirect of the entire application page
- Window: Re-direct of a pop-up (window) from the application (mother) page
The logic governing integration modes is managed by your website. Please refert to the example libraries table on our getting started with OIDC page for more details.
A couple of notes:
- Our testing tools allows you take a further look into these integration modes.
- The JS Connector may simplify the frontend integration with the OIDC Provider.
The BankID OIDC provider previously suppored inline/iframe, but this is being depreciated. New merchants should therefore choose either Redirect or Window. Read more here: https://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-10.13