Page Summary
-
Authentication requests are encrypted and signed using PGP or JWE+JWS and then encoded with web-safe base64.
-
The
AuthenticationRequestobject contains a requiredrequestIdfield, which is a string identifier with specific character limitations. -
The
requestIdhas a maximum length of 100 characters and permits only alphanumeric characters, colons, hyphens, and underscores.
Object sent during authentication request.
Here's an example of a clear text JSON request:
{
"requestId": "375dhjf9-Uydd:_"
}
The AuthenticationRequest is encrypted and signed using PGP or JWE+JWS. Further, this value is web-safe base64 encoded. This encoding is referred to below as Base64UrlEncode. In other words, the clear text JSON version of the AuthenticationRequest must be passed through the following functions:
Base64UrlEncode(
PGPSignAndEncrypt(
{
"requestId": "375dhjf9-Uydd:_"
}
)
)
or
Base64UrlEncode(
JWSignAndEncrypt(
{
"requestId": "375dhjf9-Uydd:_"
}
)
)
| JSON representation |
|---|
{ "requestId": string } |
| Fields | |
|---|---|
requestId |
REQUIRED: Identifier for this request. This is a string that has a max length of 100 characters, and contains only the characters "a-z", "A-Z", "0-9", ":", "-", and "_". |