3.1. HIE-CM- Link token generation

HIP Implementation
#1

getting 403 forbidden of https://dev.abdm.gov.in/hiecm/api/v3/token/generate-token this endpoint

image
image1138×896 59.2 KB

image
image1223×957 62.3 KB

and my client id is SBX_003058

#2

please provide the access my client id is SBX_003058

#3

Hi @IntegrationSupport,

We are getting : “User is NOT authorized to access the Resource. API Subscription validation failed.”
for https://dev.abdm.gov.in/hiecm/api/v3/token/generate-token
Can you please provide access to our client ID SBX_001854

Thanks

#4

HI @IntegrationSupport,

Can you please provide access to our client ID SBX_001854 for hiecm API.

We are stalled here.

Thanks

Satyadeep

#5

@satyadeep We have requested for V3 access for M2 to the technical team.

#6

Can you also grand us the access to v3 APIs our client ID is SBX_002015 @IntegrationSupport

#7

SBX_001854 ;SBX_002015 – we will assign roles. please give us sometime

#8

HI @IntegrationSupport, any update on this. Our development is stalled here.
Thanks

#9

@satyadeep This is resolved.

#10

HI @IntegrationSupport,
I am still getting the same error:

POST /hiecm/api/v3/token/generate-token HTTP/1.1
Host: dev.abdm.gov.in
Cookie: TS011c04bd=01445fed04280ac426ea7688a18f80d7466405b9c04b79a78e9710e3856da882b44ec52bdb850afd21e8817b65449aac0d91d3c912
Content-Type: application/json
User-Agent: insomnia/2023.5.8
REQUEST-ID: dfbf8a09-16d2-40fd-bd85-1e674c44564b
TIMESTAMP: 2024-02-13T07:46:00.873Z
X-CM-ID: SBX
X-HIP-ID: INTL-001
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE3MDc0OTYyMDIsImlhdCI6MTcwNzQ5NTAwMiwianRpIjoiZjMzMmFiZGYtOTM3OS00NjI2LWFmYTgtYjdlNzIxODY3MGNlIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiI5NDE1YmQ0Mi0yZTIxLTQ3NzQtYWFjNS1kODQ5OGNkNDE0YTAiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAxODU0Iiwic2Vzc2lvbl9zdGF0ZSI6IjE0ZWZiYjRlLWE4M2EtNDM5ZS04YTg4LWRiMWQzODI0OGVlZSIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwiT0lEQyIsImhpcCIsImhwX2lkIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiU0JYXzAwMTg1NCI6eyJyb2xlcyI6WyJ1bWFfcHJvdGVjdGlvbiJdfSwiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgZW1haWwgcHJvZmlsZSIsImNsaWVudElkIjoiU0JYXzAwMTg1NCIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwiY2xpZW50SG9zdCI6IjEwLjIzMy42Ny4yNDIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJzZXJ2aWNlLWFjY291bnQtc2J4XzAwMTg1NCIsImNsaWVudEFkZHJlc3MiOiIxMC4yMzMuNjcuMjQyIn0.CkD-3qABya2zFX4UiB_vpsRVcr6NxrHLweSvRYEqV30pZbAgP-SuYZumugAP7mMCOui6tPgXgAmGK1VLh0ZOs30E679Dd0mSK8peXUIz6-ZF06IaohGxQnXX1zjgr8mEhCSwx_CT9sVBwGChzTbdfSF5gb8jnNxnXUIpME-n_V9KMjHjhbZblm9fZAPJMySmX3RCOTkjXmDiVWsFm7mPrwn5SxYE4p6XDGpViBQacH9IosFmJyNId4zFak_dIOMvgQxWFQCQTXX9xEil2p018v_kA6kYCQ4GVXpVY3D5JFlGTrifYxpaDhgPo7UoDKOzsvw_bGyjBTbZnsM2X3DcxA
Accept: /
Content-Length: 110

| {“abhaNumber” : “91-6612-5848-5043”,
| “Name” : “Satyadeep Kumar”,
| “Gender” : “F”,
| “yearOfBirth” : “1978”
| }

  • TLSv1.2 (IN), TLS header, Supplemental data (23):
  • Mark bundle as not supporting multiuse

< HTTP/1.1 401 Unauthorized
< x-request-id: 3fd58dc8-cfcf-9997-a94e-2796ba3184c4
< cookie:
< x-forwarded-proto: http
< access-control-allow-origin:
< access-control-allow-methods: POST
< www-authenticate: null Bearer realm=“WSO2 API Manager” null, error=“invalid_token”, error_description=“The provided token is invalid”
< x-b3-sampled: 1
< x-forwarded-for: 100.65.201.149
< request-id: dfbf8a09-16d2-40fd-bd85-1e674c44564b
< access-control-allow-headers: authorization,Content-Type,SOAPAction,apikey,Internal-Key,TIMESTAMP,X-HIP-ID,REQUEST-ID,X-CM-ID,Authorization
< x-envoy-attempt-count: 1
< activityid: b9c34f3c-3a5b-4f1f-9435-4a30e896ac70
< access-control-expose-headers:
< x-cm-id: SBX
< x-envoy-external-address: 100.65.201.149
< x-b3-spanid: 5e79660f8f56a069
< x-b3-traceid: 22f04bcfe8ae2bc65e79660f8f56a069
< x-hip-id: INTL-001
< timestamp: 2024-02-13T07:46:00.873Z
< content-type: application/json; charset=UTF-8
< date: Tue, 13 Feb 2024 07:46:01 GMT
< x-envoy-upstream-service-time: 2
< X-Frame-Options: DENY
< X-XSS-Protection: 1; mode=block
< X-Content-Type-Options: nosniff
< Strict-Transport-Security: max-age=16070400; includeSubDomains
< Referrer-Policy: strict-origin
< Transfer-Encoding: chunked

#11

still showing the error {
“code”: “900908”,
“message”: "Resource forbidden ",
“description”: “User is NOT authorized to access the Resource. API Subscription validation failed.”
} our client ID is SBX_002015

#12

@GrapesDEV We have requested for v3 access, however request not to put multiple request in devforum as this creates miscommunication due to multiple similar threads.