Get the reponses from init challenge, finalize challenge and challenge api to identify if user needs to be challenged further.

put

/authn/v1

Update the authn status within UAS. Also returns if more challenge is required for the user or can return success for the user. Internally can call validate to verfiy the passed parameters with factors which are passive.

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/xml ()
Root Schema : schema
Type: object
The object defines the request parametes for update authentication request.
Show Source
  • answer provided by the user to be passed to factor.
  • InitChallengeData
    Information about the user and user's registration for challenge factor.
  • Requested operation to perform on the challenge API. It can be one of Init/Validate/Finalize. For init nonce is optional. Validate/Finalize nonce is required.
  • Result of the challenge. One of Success/Error/Failure. Validate will result in invocation of passive factor api to validate ChallengeAnswer. If the factor is not passive, exception will be thrown. Other result will be passed directly to finalize challenge call.
  • Reason for challenge result if it is failure. One of wrong_answer/too_many_attempts/channel_comm_error/other_error/unavailable_for_user/user_abandoned/user_timedout.
  • transaction id provided by the challenge api. Also this field contains previous id used within the session to update store.
  • random string to identify the future request. This will change in each response and the lastest nonce is expected in the finalize call.
Nested Schema : InitChallengeData
Type: object
Information about the user and user's registration for challenge factor.
Show Source
Nested Schema : factorAttributes
Type: array
Show Source
Nested Schema : UserFactorAttribute
Type: object
A map represented as an array of entries.
Show Source
Request Body - application/json ()
Root Schema : schema
Type: object
The object defines the request parametes for update authentication request.
Show Source
  • answer provided by the user to be passed to factor.
  • InitChallengeData
    Information about the user and user's registration for challenge factor.
  • Requested operation to perform on the challenge API. It can be one of Init/Validate/Finalize. For init nonce is optional. Validate/Finalize nonce is required.
  • Result of the challenge. One of Success/Error/Failure. Validate will result in invocation of passive factor api to validate ChallengeAnswer. If the factor is not passive, exception will be thrown. Other result will be passed directly to finalize challenge call.
  • Reason for challenge result if it is failure. One of wrong_answer/too_many_attempts/channel_comm_error/other_error/unavailable_for_user/user_abandoned/user_timedout.
  • transaction id provided by the challenge api. Also this field contains previous id used within the session to update store.
  • random string to identify the future request. This will change in each response and the lastest nonce is expected in the finalize call.
Nested Schema : InitChallengeData
Type: object
Information about the user and user's registration for challenge factor.
Show Source
Nested Schema : factorAttributes
Type: array
Show Source
Nested Schema : UserFactorAttribute
Type: object
A map represented as an array of entries.
Show Source
Back to Top

Response

Supported Media Types

200 Response

Success
Body ()
Root Schema : UpdateAuthnResponse
Type: object
The update response object.
Show Source
Nested Schema : StatusInfo
Type: object
Status of the fetch challenge info request. It contains the information required to process the user authentication request.
Show Source
  • Code representing the challenge status.
  • Error message generated if the server is unable to process the request.
  • status of the fetch challenge info for user request. It will be one of the following authenticated/pending verification/pending identification/failed/error/missing registration/challenge blocked.
Nested Schema : InitContext
Type: object
Show Source
Nested Schema : challengeInfo
Type: array
A user can be challenged in many ways, the object will contain all the possible ways a user can be authenticated. In case the user information is not available in the request, the Default challenge mechanism as per the service provider configuration will be present.
Show Source
Nested Schema : cookies
Type: array
Cookies present in the user access request.
Show Source
Nested Schema : factorAttributes
Type: array
Show Source
Nested Schema : requestParams
Type: array
Show Source
Nested Schema : UserFactorAttribute
Type: object
A map represented as an array of entries.
Show Source
Nested Schema : KeyValPair_2
Type: object
Key-value pair which can be used generically.
Show Source
Nested Schema : value
Type: object
Content that needs to be provided.
Nested Schema : FactorChallengeInfo
Type: object
information required to process user request using the factors available to it will be present in the object.
Show Source
Nested Schema : FactorContext
Type: object
The context required by factor to process the user authentication request.
Show Source
Nested Schema : challengeAttrMap
Type: array
Show Source
Nested Schema : prompts
Type: array
the display prompt will contain one or more prompts that can be further selected by user.
Show Source
Nested Schema : FactorAttribute
Type: object
A map represented as an array of entries.
Show Source
Nested Schema : Prompt
Type: object
Prompt the can be displayed to end user
Show Source
Nested Schema : KeyValPair
Type: object
Key-value pair which can be used generically.
Show Source
Nested Schema : value
Type: object
associated value.

400 Response

if the update authn failed due to validation of parameters.
Body ()
Root Schema : AuthnAPIResponse
Type: object
Show Source
Back to Top