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.
= Supported. = In progress / future support.
|XID||Default. Corresponds to 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 xID in this way implies step-up to BankID whenever required. Hence, XID always returns sucess, unless the end–user aborts any BankID step-stepup up in progress.
The merchant starts XID 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-userunsolicited, step-up to BankID never happens. XID Hence, xID returns sucess only if the end-user device is recognized by XID.
|XID:noclickunsolicited:noacceptFOR FUTURE IMPLEMENTATION. nodialog||Builds on XID:noclickunsolicted with the additional restriction that XID immediately returns false in cases where an xID-dialog would otherwise be shown, typically when the end-user device is recognized by xID but has never been used at the merchant in question before. This login_hint can be used to probe silently if the visiting user can be recognized, and if that is not the case allowing the merchant to start xID again with one of the other login_hints.|