Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate OTP Issues #84

Open
3 tasks done
SIA-iOS-Dev opened this issue Jun 27, 2024 · 0 comments
Open
3 tasks done

Validate OTP Issues #84

SIA-iOS-Dev opened this issue Jun 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@SIA-iOS-Dev
Copy link

Checklist

  • The issue can be reproduced in the attached sample application in the repository.
  • I have read the relevant SDK documentation and have not found a suitable solution or answer.
  • I agree to the terms within the SAP Code of Conduct.

Description

We launch the native screensets to register a new user

Reproduction

  1. Native Screen sets makes the accounts.register API call, and we receive an "Account pending verification" error.
  2. We dismiss the native screensets and call the accounts.otp.sendCode API to send an OTP, which the user receives via email.
  3. When we try to verify the OTP using the accounts.otp.update API, we encounter an error with errorCode: 403007 and errorMessage: Permission denied.
  4. If we call accounts.auth.otp.verify, we get a success response, but the user remains unverified.
  5. Attempting to log in using the accounts.otp.login with the OTP, API results in an "Authentication method is currently disabled" error.
  6. If we try to log in with accounts.login, we receive an "Account Pending verification" error.

Can you please advise us on the correct flow to send and validate the OTP?

Additional context

No response

SDK version

1.6.1

@SIA-iOS-Dev SIA-iOS-Dev added the bug Something isn't working label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant