Getting error on auth/init

Hi. I’m getting error for auth/init call

auth/init request payload

  "requestId": "0a9fd731-11b4-4e0b-98ab-e1d23ae4b3af",
  "timestamp": "2023-01-24T03:34:08.600Z",
  "query": {
    "id": "zelda@sbx",
    "purpose": "KYC_AND_LINK",
    "authMode": "MOBILE_OTP",
    "requester": {
      "type": "HIP",
      "id": "Bahmni"
    }
  }
}

auth/on-init response

  "requestId": "57d54f96-ccbc-47b9-80bc-c14120a07aec",
  "timestamp": "2023-01-24T03:34:11.532433",
  "auth": null,
  "error": {
    "code": 1510,
    "message": null
  },
  "resp": {
    "requestId": "ae429ba9-b482-4c29-9a33-b65129c2db4f"
  }
}

But I’m receiving otp. pls check @IntegrationSupport @Shubhanshu_S

I’m also getting same error.
As per this link https://github.com/ProjectEKA/projecteka.github.io/wiki/API-Error-Codes

1510 error code belongs to Bad request from Gateway.

We have HTC Demo today and this error is coming :frowning:

@IntegrationSupport @admin @Binay.n.Singh

HTC scheduled for today has been cancelled.

OK.
Can we ensure such things does not happen when HTC demo is scheduled, We have rescheduled HTC demo for 2 time due to sandbox API issues. 1. was health data transfer API was not getting initiated from gateway and another was this /auth-int api call error.

Don’t we have any automation testing in place to know this in advance and then schedule HTC demo?

Issue is again happening. Pls check @IntegrationSupport

Hello @IntegrationSupport @Shubhanshu_S The same issue started happening again on sandbox. Facing this for the last two hours. Pls check and revert. Thanks

auth/init request

{
    "requestId": "42cc3492-cfd5-46e9-afae-c6ce61fb2f4c",
    "timestamp": "2023-02-01T11:04:13.557000",
     "query": {
        "id": "mohan2005@sbx",
        "purpose": "KYC_AND_LINK",
        "authMode": "MOBILE_OTP",
        "requester": {
            "type": "HIP",
            "id": "JSS_DEV_TEST"
        }
    }
}

auth/on-init response

{
    "requestId": "b2fbb880-3942-45ef-bd8b-988d9e3ab090",
    "timestamp": "2023-02-01T11:04:14.378921",
    "auth": null,
    "error": {
        "code": 1510,
        "message": null
    },
    "resp": {
        "requestId": "5589bb92-da18-4a9b-8b34-e386c5a0a36e"
    }
}

but still OTP is coming up on my mobile

Hi @IntegrationSupport, Please check this on priority. Many more developers getting this now. We are also getting the same problem.

{
     "requestId": "{{$guid}}",
     "timestamp": "{{timestamp}}",
     "query": {
        "id": "daivat@sbx",
        "purpose": "KYC_AND_LINK",
        "authMode": "MOBILE_OTP",
        "requester": {
            "type": "HIP",
            "id": "HIP7M"
        }
    }
}

We are getting OTP in mobile. But auth/on-init we are getting following.

{
    "requestId": "3f11b9f7-6cd7-4471-8f3b-fb7d094ca209",
    "timestamp": "2023-02-01T12:36:49.106666",
    "auth": null,
    "error": {
        "code": 1510,
        "message": null
    },
    "resp": {
        "requestId": "35cc8f46-3ddf-42e7-92c9-5f9a8ad37caa"
    }
}

Please reply back on this asap.

Thank you.

Hi @IntegrationSupport I am also getting the same error and have been facing this issue since yesterday.
{
“requestId”: “{{$guid}}”,
“timestamp”: “{{timestamp}}”,
“query”: {
“id”: “91236020572319@sbx”,
“purpose”: “KYC_AND_LINK”,
“authMode”: “MOBILE_OTP”,
“requester”: {
“type”: “HIP”,
“id”: “jatayu_demo_id”
}
}
}

I am receiving the otp but the response I get is
{
“requestId”: “75f37e1e-d986-409c-8b47-4f986ec68315”,
“timestamp”: “2023-02-02T07:30:52.333575”,
“auth”: null,
“error”: {
“code”: 1510,
“message”: null
},
“resp”: {
“requestId”: “2270e932-56dd-4c2a-9743-b7d9bb015caf”
}
}

Hi @IntegrationSupport. Getting 400 bad request intermittently on auth/on-init for the same payload

Request Payload

{
  "requestId": "27fac286-9c51-4540-afd2-91ef8b1336bf",
  "timestamp": "2023-02-06T13:37:26.772Z",
  "query": {
    "id": "rimarai@sbx",
    "purpose": "LINK",
    "authMode": "MOBILE_OTP",
    "requester": {
      "type": "HIP",
      "id": "Bahmni"
    }
  }
}

Response on auth/on-init

{
  "requestId": "9c8fc3ba-80a4-4fb7-9cc2-3c57334b0919",
  "timestamp": "2023-02-06T13:34:23.627417",
  "auth": null,
  "error": {
    "code": 1510,
    "message": "400 Bad Request from POST http://gateway:8000/v0.5/users/auth/on-init"
  },
  "resp": {
    "requestId": "758f4557-29fb-4aa4-b492-973a6b33d1dc"
  }
}

The issue with these flows been there for a while. Pls Check as soon as possbile

Hi @SanoferSameera make sure the HIP you are using is valid, we are getting the callback response on webhook. PFA screenshot.

Hi @Ramandeep1. yeah It is working now. but not receiving auth/on-confirm callback intermittently

Hi @SanoferSameera please make sure system settings at your infra level are working fine, firewall settings etc. as we are able to receive the callback within seconds.

Thanks

@Ramandeep1 Im also facing same issue, somtimes im not getting callback on /on-init, /on-fetch-auth-modes, /on-confirm api.

Can we have access to backend logs to troubleshoot the issue??

Im not getting callback for mobile and Aadhar OTP flow, only getting callback on demographics mode and its again further its again callback api for /confirm is not getting called.

Payload for /init api for MOBILE OTP
{
“requestId”: “1ba94876-70ca-477f-af93-5fc6fcf55712”,
“timestamp”: “2023-02-12T08:09:42.213000”,
“query”: {
“id”: “ashutosh.abhatest2@sbx”,
“purpose”: “KYC_AND_LINK”,
“authMode”: “MOBILE_OTP”,
“requester”: {
“type”: “HIP”,
“id”: “IN3410000303”
}
},
}

Payload for Aadhaar OTP:

{
  "requestId": "26159f76-dcb9-4593-a6db-3ed8ef5a8ec3",
  "timestamp": "2023-02-12T08:11:29.403000",
  "query": {
    "id": "ashutosh.abhatest2@sbx",
    "purpose": "KYC_AND_LINK",
    "authMode": "AADHAAR_OTP",
    "requester": {
      "type": "HIP",
      "id": "IN3410000303"
    }
  }
}

is it becuase facility portal ? im not able to access test facilities I have created.

Following API is failing.
https://facilitysbx.ndhm.gov.in/hirClaimedFacility

form encoded parameters:
searchId=&healthId=14-6200-5683-8807&facilityId=&facilityName=&token=eyJhbGciOiJSUzUxMiJ9.eyJzdWIiOiIxNC02MjAwLTU2ODMtODgwNyIsImV4cCI6MTY3NjE5MTY3NCwiaWF0IjoxNjc2MTg5ODc0fQ.oxSDhNOmmVeMzDi8Eh_Xy9n4ZmHvagpJ35QZzQ5w3d2oCOBDIwjlmu4eGDFgcIYCFRjAs9ilOxIoxigENDBe2yKLoEqQmeWNwpTKnSOgWWG4sonkm2pz6d2TohFzEuhmrGdQaRvobz6TJ229puzIkzpRzTm2_mZ3Dmxo97ZyvADBA0C5lCPpeYAfmJ5Qb0U7kHbbPId1tsRsd-CzHP1EsOZ2J3iq79UlyfptTZk9_ZkM2UKvX1Iyog-oUZFmJ7uHTJTVJeREhZR_v1hv60_SzEtvUeplOc5adRz9a5uioSuawI8rjvCmzD9veW_-J9gyt0YIlNnTX3oLyBW9UD36Gw

Hi @cloops_ashutosh you have to create facility via https://facilitysbx.ndhm.gov.in/ and that facility must be approved, after that you can access that or you can use some existing ones.

Thanks

@cloops_ashutosh - please refer the document upload on [https://facilitysbx.ndhm.gov.in/] (please refer the documents under menu, ‘resources’ )

I have created facilities on this portal only.

https://facilitysbx.ndhm.gov.in/

it was working earlier , now its showing error.

Can you please help clarify in steps what is it that you are trying to achieve? Are the apis working? Are you facing concern with the registration of facility or linkage?

So issue was im not getting callback on /on-init, /on-fetch-auth-modes, /on-confirm api during ABHA verification process. But now its working fine. Its working some-times and not working some-times.

We have to try again and again and again. Thats the only issue. Last year all the APIs were working very smooth. This year only im seeing many issues in existing API’s.

Is this issue solved?