...
Info |
---|
An in detail documentation off the possible parameters can be found in the OIDC specification. |
Parameters
Parameter | Example | Value |
---|---|---|
| oidc email profile | The requested scopes that define what data will be available to the client. |
| code | Impacts the OIDC flow.
|
| 01d084c3a2a44043b28934d6a9dde00d | The identifier of the client. |
| https://my.application.ch/signing-oidc | Where the user will be redirected to after a successful authentication. |
| 4af227e317634c2e8000e4cb3a67ddf4 | Opaque value to contain the state. The authentication server will send that state back to the client. |
| form_post | Impacts the return mode of the request. |
| fbf6481c19244b9581fd1df815f719ef | String value used to associate a Client session with an ID Token, and to mitigate replay attacks. |
| ASCII string value that specifies how the Authorization Server displays the authentication and consent user interface pages to the End-User. | |
| login | Space delimited, case sensitive list of ASCII string values that specifies whether the Authorization Server prompts the End-User for reauthentication and consent.
|
| 90 | Maximum Authentication Age in seconds. |
| de | Determinates the UI language. |
| e79d58a3a157447294869651cc5ec877 | ID Token previously issued by the Authorization Server being passed as a hint about the End-User's current or past authenticated session with the Client. |
| username | Can indicate the user that needs to authenticate. |
|
| See the https://itsense.atlassian.net/wiki/spaces/IKB/pages/486965311/Level+of+Authentication#ACR-Values |