Package io.jans.as.model.ciba
Class BackchannelAuthenticationRequestParam
java.lang.Object
io.jans.as.model.ciba.BackchannelAuthenticationRequestParam
- Version:
- May 28, 2020
- Author:
- Javier Rojas Blum
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final String
Requested Authentication Context Class Reference values.static final String
A human readable identifier or message intended to be displayed on both the consumption device and the authentication device to interlock them together for the transaction by way of a visual cue for the end-user.static final String
static final String
static final String
static final String
A bearer token provided by the Client that will be used by the OpenID Provider to authenticate the callback request to the Client.static final String
static final String
An ID Token previously issued to the Client by the OpenID Provider being passed back as a hint to identify the end-user for whom authentication is being requested.static final String
A hint to the OpenID Provider regarding the end-user for whom authentication is being requested.static final String
A token containing information identifying the end-user for whom authentication is being requested.static final String
An public static final String containing all data about the request as a single JWTstatic final String
Url where OP could get the request object related to the authorization.static final String
A positive integer allowing the client to request the expires_in value for the auth_req_id the server will return.static final String
The scope of the access request.static final String
A secret code, such as password or pin, known only to the user but verifiable by the OP. -
Method Summary
-
Field Details
-
SCOPE
The scope of the access request. CIBA authentication requests must contain the openid scope value. Other scope values may be present.- See Also:
-
CLIENT_NOTIFICATION_TOKEN
A bearer token provided by the Client that will be used by the OpenID Provider to authenticate the callback request to the Client. Required if the Client is registered to use Ping or Push modes.- See Also:
-
ACR_VALUES
Requested Authentication Context Class Reference values.- See Also:
-
LOGIN_HINT_TOKEN
A token containing information identifying the end-user for whom authentication is being requested.- See Also:
-
ID_TOKEN_HINT
An ID Token previously issued to the Client by the OpenID Provider being passed back as a hint to identify the end-user for whom authentication is being requested.- See Also:
-
LOGIN_HINT
A hint to the OpenID Provider regarding the end-user for whom authentication is being requested.- See Also:
-
BINDING_MESSAGE
A human readable identifier or message intended to be displayed on both the consumption device and the authentication device to interlock them together for the transaction by way of a visual cue for the end-user.- See Also:
-
USER_CODE
A secret code, such as password or pin, known only to the user but verifiable by the OP. The code is used to authorize sending an authentication request to user's authentication device.- See Also:
-
REQUESTED_EXPIRY
A positive integer allowing the client to request the expires_in value for the auth_req_id the server will return.- See Also:
-
REQUEST
An public static final String containing all data about the request as a single JWT- See Also:
-
REQUEST_URI
Url where OP could get the request object related to the authorization.- See Also:
-
CLIENT_ID
- See Also:
-
CLIENT_SECRET
- See Also:
-
CLIENT_ASSERTION_TYPE
- See Also:
-
CLIENT_ASSERTION
- See Also:
-