The OIDC Provider from BankID supports codification of amr values as part of the login_hint request parameter to the Authorize endpoint. Hence, pre-selection of the xID IPD can be governed by suppling proper values as shown in the following table. The OIDC Client may alternatively use the xID Connector to select the xID IDP and govern its behaviour.
login_hint | Description |
|---|---|
| XID | Default. Corresponds to XID:userintent |
| XID:userintent | The merchant starts xID as the result of an explicit intent from the end-user, typically as the result of the end-user clicking an xID-button displayed by the merchant. Initiating XID in this way implies step-up to BankID whenever required. Hence, XID always returns sucess, unless the end–user aborts any BankID-stepup in progress. |
| XID:unsolicited | The merchant starts XID unsolicited without any explicit intent from the end-user, typically in conjuction with page-visit / page-load without any prior click on an XID-button by the end-user. Since initiating XID in this way is not an intent from the end-user, step-up to BankID never happens. XID returns sucess only if the end-user device is recognized by XID. |
| XID:noclick:noaccept | FOR FUTURE IMPLEMENTATION. Builds on XID:noclick |