Identity Management (MOSC)

MOSC Banner

Validate TOTP generated by OMA with the ValidateOTP REST API

edited Jul 1, 2020 5:07AM in Identity Management (MOSC) 2 commentsAnswered

According to 12c PS4 documentation the ValidateOTP endpoint is able to validate TOTP generated by OMA.

So User install OMA on their phone, the secret key is configured and now OMA is generating TOTP for the user.

When calling the ValidateOTP REST API endpoint, it has 4 mandatory fields:-

  1. User ID
  2. OTP
  3. correlationId
  4. appName

Now the correlationId and appName fields make sense when the OTP is generated using the CreateOTP REST api but for TOTP generated by OMA these fields have no values and the api call keep complaining about Null or empty correlationId and appName

Has anyone solved this issue.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center