We do not receive AADHAAR_OTP as an authentication mode in the API - /v0.5/users/auth/on-fetch-modes.
Abha ID is ajeet2041@sbx and is linked to Aadhar card.
Note: We were receiving this mode before.
Hi @IntegrationSupport,
Could you please assist on this ?
We do not receive AADHAAR_OTP even in M1 API - https://healthidsbx.abdm.gov.in/api/ for an id linked with aadhaar.
@ayadav Aadhaar OTP is received from UIDAI. OTP is not sent by ABDM gateway for this mode. Please try with another phone number linked to another aadhaar and be in network area to receive OTP.
Hi @IntegrationSupport,
Thanks for the reply. We are aware of the OTP sent through UIDAI.
We are not receiving AADHAAR_OTP as an option from the API https://healthidsbx.abdm.gov.in/api/v1/search/searchByHealthId in the authMethods in the response body.
(Tried with a couple of phone numbers)
See below:
“authMethods”: [
“DEMOGRAPHICS”,
“MOBILE_OTP”,
“AADHAAR_BIO”
],
@ayadav Please change Mobile_OTP to Aadhaar_OTP in the payload body if you are not getting the option from the API.
We are using the API https://healthidsbx.abdm.gov.in/api/v1/search/searchByHealthId to get the auth methods available for the health id.
Based on that, we allow the user to select the Auth method for verification of ABHA in our application.
We cannot directly add Aadhaar_OTP for the auth initiation as it may not be available for all health ids.
(There is a mandatory test case that needs to be passed for the verification of ABHA using Aadhaar)
Hi @IntegrationSupport,
Any update on this issue ? Can the associated test cases (5.1 and 5.2 in M1) be considered as optional ?
@ayadav Yes, not required test case 5.2. However, 5.1 you have to implement, that is creation of ABHA address
5.1 and 5.2 are both for ABHA Verification - Same test case basically one for abha no and other for abha address.
Can you confirm these both are not mandatory ?
We are able to do verification using Mobile OTP.
@ayadav Both are mandate. Because once you create ABHA address and ABHA number, both need to be verified too. And these two steps are for returning users.
Hi @IntegrationSupport, any update on this issue? Request you to pass on to tech team to look into this issue.
Can somebody check I’m getting “Token verification failed” response on v0.5/users/auth/on-fetch-modes
from morning? is it for me only or everyone…? Yesterday night it was working though
@ayadav for Aadhaar OTP option, you need to replace and type Aadhaar OTP in the body in place of mobile OTP auth mode.
This is same as the earlier response and not helpful in our case. Like I said earlier we rely on the API https://healthidsbx.abdm.gov.in/api/v1/search/searchByHealthId to dynamically select the auth mode returned. Would be great if the issue is resolved and we receive the option from the said API.
@ayadav For search by healthid api, two options are there aadhaar otp and mobile otp. Both are working fine.
| Login via Aadhaar OTP | 2.1.1 | v1/auth/confirmWithAadhaarOtp |
|---|---|---|
| 2.1.2 | v2/registration/aadhaar/checkAndGenerateMobileOTP | |
| Login via Mobile OTP | 2.2.3 | v1/auth/confirmWithMobileOTP |