Complete Factor Verification

patch

/mfa/v1/requests/{requestId}

Request

Supported Media Types
Path Parameters
  • Unique identifier of a factor authentication request returned by the server, when the user initiated factor verification
Header Parameters
  • Provide a valid OAuth Access Token that has either the 'Authenticator Client' or 'MFA Client' scope.
Body ()
Complete Factor Verification Schema
Root Schema : CompleteFactorVerification
Type: object
Use this schema to complete factor verification or to resend OTP
Show Source
  • This attribute indicates the pre-generated bypass code that the user wants to use, while authenticating using BYPASSCODE method.
  • This attribute provides the one time passcode that the user received over SMS, PHONE_CALL, EMAIL or the TOTP that was generated by the Oracle Mobile Authenticator App enrolled in IDCS. This attribute is only applicable for TOTP, SMS, PHONE_CALL and EMAIL methods.
  • This contains the context/request related details in encrypted form, which needs to be passed back and forth between server and client. The details are needed by the server to process a request and are opaque to the client.
  • Attribute to indicate if the user wants the OTP to be resent to the mobile number or email id being used to authenticate. Supported values for this attribute are:
    • true
    • false
    This attribute is considered only for EMAIL, PHONE_CALL and SMS factors.
  • securityQuestions
    List of Security Questions being used for verification
Nested Schema : securityQuestions
Type: array
List of Security Questions being used for verification
Show Source
Nested Schema : SecQuesVerification
Type: object
Use this schema to complete Security Questions factor verification
Show Source
  • Answer to an enrolled security question that the user wants to use for authentication.
  • The identifier of an enrolled security question that is being used for authentication by a user.
Back to Top

Response

Supported Media Types

200 Response

Indicates successful authentication.

400 Response

Indicates that the request payload is invalid.

401 Response

Indicates unsuccessful authentication if the otpCode/security answer provided was invalid. Indicates unauthorized access if the token provided is invalid or if the user is either locked, inactive, or not enrolled in MFA.

404 Response

Indicates that the requestId provided is invalid.

500 Response

Internal Server error
Back to Top