The exact behaviour for the xID IPD can be controlled by the OIDC Client by suppling the proper values to OIDC Provider from BankID supports codification of amr values as part of the login_hint parameter in requests request parameter to the Authorize endpoint. As shown Hence, pre-selection of the xID IPD can be governed by suppling proper values as shown in the following table, note that the OIDC Provider from BankID supports codification of amr values as part of the login_hint request parameter. The OIDC Client may alternatively use the xID Connector to select the xID IDP and govern the its behaviour for the xID IPD.
login_hint | Description |
|---|---|
| XID | xID is pre-selected, with step-up to BankID whenever required |
| XID:nostepup | xID is pre-selected, but without any step-up to BankID. In this case an authentication failure is returned to the OIDC Client if xID cannot rekognize the browser/device in question. |
| XID::directconsent | xID is pre-selected and any accept dialog for the OIDC Client in question is ommited if the Client is also requesting scopes that demand concent handling |