Request Rejected in Getting QR code

#1

I have the following request
curl -X GET “https://dev.abdm.gov.in/cm/v1/apps/patients/profile/qr-code” -H “accept: application/json” -H “X-Auth-Token: Bearer eyJhbGciOiJSUzUxMiJ9.eyJzdWIiOiI5MS03MjE3LTUyMjMtMzQxMiIsImNsaWVudElkIjoiU0JYXzAwMjgyNyIsInN5c3RlbSI6IkFCSEEtTiIsIm1vYmlsZSI6IjcyMDY4ODk2MTQiLCJoZWFsdGhJZCI6InJhaHVsMjYwNzkyQHNieCIsImV4cCI6MTY4OTI2OTc4OSwiaGVhbHRoSWROdW1iZXIiOiI5MS03MjE3LTUyMjMtMzQxMiIsImlhdCI6MTY4OTI2Nzk4OX0.YYfJDgsbl_7q5iLAs0gnYSkMI4v4AQTW1laYVXnkhbbJ1FgH2JsdB_87gj0AUITy_4Vk-nQi1ynCt0f_cblh4QE5QgDzA-xrRrOsKXY5Y71t_-avt9kh3mSWjcHEcIGIHN9Sk3wTG90cRPxq67tkWfwaPIki2qNi2CdIvRn5cN1Wi9eZAa_YWYbiTvcTwnlp9qVVvF-0T6egxGAWEb1GPpmlSD__5HldDVv4ZrSMadnCMXfN6ywfdCgMChULg2YIxhj171IyWZWxRlUfI9fswiCRSyv_qv-30cnOz5d9UKjZT1mSmWaNTJ_ZVnaaJ3dgQeIv1MsgYWVQKY9t08xKhg4aPjkTV9Ml5FtzNyPxLt4K2yFXceuPIivgalifByQvtHUr6B3lrW7cAvY-uiFIUr9DU89rNltgMIfzOLJa1_PfGalSOHRBoIC7e88Hv16lt3D_jaiBek6cAI_L-GHm4vZTkt0NncKC-x_mDxOd2uF5T2SPpja9w8lXWINgp8BPiTpyqu3tSNHWgmIPJIr0Ck9NXXGp9JDpT0H_MwoGjfg30uF8CwekM0Imk0MRPvlC-jD9HrJOeJ8XVx__wWdguMNGq2AlAi_mtVWWk_khk4yXZLoHeyzsu74OKndTHb9ywZ-AI_obyq_7utzys_XTpPaJYsRGf9cWYpyCnONeosY”

I am getting the following response

Request RejectedThe requested URL was rejected. Please consult with your administrator.

Your support ID is: 5170449241242623949

[Go Back] **%**

Please let me know how to fix this

@IntegrationSupport

#2

@IntegrationSupport I am getting this error in all the APIs except the healthId APIs

#3

@rahul260792 Please confirm, are you implementing PHR mobile app. Also provide your SBX client ID and entity name.
To check role access :
Please share the jwt.io output with us. You can confirm it by passing your access token generated by //sessions API to https://jwt.io

#4

@IntegrationSupport Yes I am implementing PHR app as well. My client Id is SBX_002827
Following is the jwt.io response

{
“exp”: 1689602123,
“iat”: 1689580523,
“jti”: “16f2d96e-2d22-48d4-baca-44431f8ffee5”,
“iss”: “https://dev.ndhm.gov.in/auth/realms/central-registry”,
“aud”: “account”,
“sub”: “881ea846-4129-4729-9d85-3e8edae6adcf”,
“typ”: “Bearer”,
“azp”: “SBX_002827”,
“session_state”: “a357e3f2-0296-4829-8059-75181ae11d8b”,
“acr”: “1”,
“allowed-origins”: [
“http://localhost:9007”
],
“realm_access”: {
“roles”: [
“hiu”,
“offline_access”,
“healthId”,
“phr”,
“OIDC”,
“health_locker”,
“hip”
]
},
“resource_access”: {
“SBX_002827”: {
“roles”: [
“uma_protection”
]
},
“account”: {
“roles”: [
“manage-account”,
“manage-account-links”,
“view-profile”
]
}
},
“scope”: “openid email profile”,
“clientId”: “SBX_002827”,
“clientHost”: “10.233.67.162”,
“email_verified”: false,
“preferred_username”: “service-account-sbx_002827”,
“clientAddress”: “10.233.67.162”
}

#5

@IntegrationSupport any update on this?

#6

@rahul260792 Which API you are getting error of The requested URL rejected, please share all the API sequence along with payload body screenshot of postman.

#7

Following is the Profile Share API screenshot. I have obtained the x token from HID login APIs using the base URL https://healthidsbx.abdm.gov.in/api/

image
image1874×1514 391 KB

Following is the screenshot of body

image
image1876×1444 385 KB

In Patient auth init API I am getting the empty response too

image
image1856×1512 349 KB

image
image1860×1464 283 KB

Please let me know if anything else is required.

#8

@IntegrationSupport Let me know if anything else is required

#9

@IntegrationSupport Also the following curl is not working for me.

curl -X POST “https://dev.abdm.gov.in/cm/v1/apps/login/hid/auth-init” -H “accept: /” -H “authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2ODk4NjA4NDcsImlhdCI6MTY4OTgzOTI0NywianRpIjoiNDYwYzFkYzMtOTM1OS00ZTcxLTgzMzktOTNjZjNkMzg3NzEzIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiI4ODFlYTg0Ni00MTI5LTQ3MjktOWQ4NS0zZThlZGFlNmFkY2YiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAyODI3Iiwic2Vzc2lvbl9zdGF0ZSI6IjQ3MmU5MjFjLTdiZWItNDBkZS1iNDlhLTgzYjRjNjAwNzg3ZSIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhlYWx0aF9sb2NrZXIiLCJoaXAiXX0sInJlc291cmNlX2FjY2VzcyI6eyJTQlhfMDAyODI3Ijp7InJvbGVzIjpbInVtYV9wcm90ZWN0aW9uIl19LCJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im9wZW5pZCBlbWFpbCBwcm9maWxlIiwiY2xpZW50SWQiOiJTQlhfMDAyODI3IiwiY2xpZW50SG9zdCI6IjEwLjIzMy42Ny4yMSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXNieF8wMDI4MjciLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjY3LjIxIn0.NCCouQPPKG9A_5b93gSlYhd4XSgmSgwQlvDn0Ns7lHijB5esrfiiUdc8MZzHqLd0NdzEzHYDn-Xtm3wvF_g4Cg3Uhi4bQkflDQz-j3U-yp8BvM27U1gIeOrL0WYB10gS-vCd9lkWEvomOShqn5otLwQekuvti5BW6sD17pVc-nKU6wXufmGcK3lOwBk1jDV91Qba04NwoGFq-_4KGjn1-e8CTkJz_do7057sKlEqZfkC64AKEfRGHf4PC8vYvu9haLfXP-d_LgAPCvmWQKnW-m1DVNCn5w8BPPYGl2Sc8HrnKdxnmhxMnlLT6r0NjrBbfQGemwq4CGNp1Y89gT-81A” -H “Content-Type: application/json” -d “{“healthIdNumber”:“91-7217-5223-3412”,“purpose”:“CM_ACCESS”,“authMode”:“AADHAAR_OTP”,“requester”:{“type”:“PHR”,“id”:“SEHT_DEV_PHR”}}”

I get connection timed out for this

#10

@rahul260792 Wrong payload used for patients/profile share API. For API v1/apps/login/hid/auth-int - Use mobile OTP in the payload body instead of Aadhaar OTP.

For reference sharing swagger link :https://sandbox.abdm.gov.in/swagger/ndhm-phr-app2.yaml
https://sandbox.abdm.gov.in/swagger/ndhm-phr-app.yaml

#11

@IntegrationSupport I tried phr-app2 swagger I am getting the following error

image
image1456×1160 107 KB

I also tried the following CUrl. It gives me empty response

curl -X POST “https://dev.abdm.gov.in/cm/v1/apps/login/hid/auth-init” -H “accept: /” -H “Content-Type: application/json” -H “Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2ODk4NjU3NzMsImlhdCI6MTY4OTg0NDE3MywianRpIjoiYzZkNTlmYjUtYmYxOC00OTU1LTlmMGUtMTI5M2E1N2M4OTRjIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiI4ODFlYTg0Ni00MTI5LTQ3MjktOWQ4NS0zZThlZGFlNmFkY2YiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAyODI3Iiwic2Vzc2lvbl9zdGF0ZSI6IjRlMWMwMGMyLTQwOGYtNDFkMy1hZDdiLTFjN2U1ZDMxMTlhZiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhlYWx0aF9sb2NrZXIiLCJoaXAiXX0sInJlc291cmNlX2FjY2VzcyI6eyJTQlhfMDAyODI3Ijp7InJvbGVzIjpbInVtYV9wcm90ZWN0aW9uIl19LCJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im9wZW5pZCBlbWFpbCBwcm9maWxlIiwiY2xpZW50SWQiOiJTQlhfMDAyODI3IiwiY2xpZW50SG9zdCI6IjEwLjIzMy42Ny4yMSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXNieF8wMDI4MjciLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjY3LjIxIn0.L8lA6b63-dQlnRHCpmo-hAgLXfntdDdD105wTDij7Zt8-u511hfMLJnPeZIBLni7ZSFngYFgYfdOnEemyMtzsKRfRW1ezPh1ScYzJhgrNtlfIIcM5l5OzpSfy8fsTbzLePebJKZw00WKz8eYHmPqqClk9-v9tl2KtLBDWBv6WdBDchbxoMo40mAErCjzxicO0PNl7lYXy_Oe_VnRlTiypIzOaFHmgC7WMoUUelU6voXwFJw-6F72iRpplImESH2Nmcna6rWDGojfrMFTUKf36jLgZT9xZKL-X4nZEB6t5h2S1pLIIVPXW9yJCo41M_xN0EKRz3OUrdunivN8h3mUwg” -d “{“healthIdNumber”:“91-7217-5223-3412”,“purpose”:“CM_ACCESS”,“authMode”:“MOBILE_OTP”,“requester”:{“type”:“PHR”,“id”:“SEHT_DEV_PHR”}}”

#12

@IntegrationSupport when I try the following curl for the url cm/v1/apps/auth-init

curl -X POST “https://dev.abdm.gov.in/cm/v1/apps/auth-init” -H “accept: application/json” -H “Content-Type: application/json” -H “Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJBbFJiNVdDbThUbTlFSl9JZk85ejA2ajlvQ3Y1MXBLS0ZrbkdiX1RCdkswIn0.eyJleHAiOjE2ODk4NjU3NzMsImlhdCI6MTY4OTg0NDE3MywianRpIjoiYzZkNTlmYjUtYmYxOC00OTU1LTlmMGUtMTI5M2E1N2M4OTRjIiwiaXNzIjoiaHR0cHM6Ly9kZXYubmRobS5nb3YuaW4vYXV0aC9yZWFsbXMvY2VudHJhbC1yZWdpc3RyeSIsImF1ZCI6ImFjY291bnQiLCJzdWIiOiI4ODFlYTg0Ni00MTI5LTQ3MjktOWQ4NS0zZThlZGFlNmFkY2YiLCJ0eXAiOiJCZWFyZXIiLCJhenAiOiJTQlhfMDAyODI3Iiwic2Vzc2lvbl9zdGF0ZSI6IjRlMWMwMGMyLTQwOGYtNDFkMy1hZDdiLTFjN2U1ZDMxMTlhZiIsImFjciI6IjEiLCJhbGxvd2VkLW9yaWdpbnMiOlsiaHR0cDovL2xvY2FsaG9zdDo5MDA3Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJoaXUiLCJvZmZsaW5lX2FjY2VzcyIsImhlYWx0aElkIiwicGhyIiwiT0lEQyIsImhlYWx0aF9sb2NrZXIiLCJoaXAiXX0sInJlc291cmNlX2FjY2VzcyI6eyJTQlhfMDAyODI3Ijp7InJvbGVzIjpbInVtYV9wcm90ZWN0aW9uIl19LCJhY2NvdW50Ijp7InJvbGVzIjpbIm1hbmFnZS1hY2NvdW50IiwibWFuYWdlLWFjY291bnQtbGlua3MiLCJ2aWV3LXByb2ZpbGUiXX19LCJzY29wZSI6Im9wZW5pZCBlbWFpbCBwcm9maWxlIiwiY2xpZW50SWQiOiJTQlhfMDAyODI3IiwiY2xpZW50SG9zdCI6IjEwLjIzMy42Ny4yMSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwicHJlZmVycmVkX3VzZXJuYW1lIjoic2VydmljZS1hY2NvdW50LXNieF8wMDI4MjciLCJjbGllbnRBZGRyZXNzIjoiMTAuMjMzLjY3LjIxIn0.L8lA6b63-dQlnRHCpmo-hAgLXfntdDdD105wTDij7Zt8-u511hfMLJnPeZIBLni7ZSFngYFgYfdOnEemyMtzsKRfRW1ezPh1ScYzJhgrNtlfIIcM5l5OzpSfy8fsTbzLePebJKZw00WKz8eYHmPqqClk9-v9tl2KtLBDWBv6WdBDchbxoMo40mAErCjzxicO0PNl7lYXy_Oe_VnRlTiypIzOaFHmgC7WMoUUelU6voXwFJw-6F72iRpplImESH2Nmcna6rWDGojfrMFTUKf36jLgZT9xZKL-X4nZEB6t5h2S1pLIIVPXW9yJCo41M_xN0EKRz3OUrdunivN8h3mUwg” -d “{“patientId”:“rahul260792@sbx”,“purpose”:“CM_ACCESS”,“authMode”:“MOBILE_OTP”,“requester”:{“type”:“PHR”,“id”:“SEHT_DEV_PHR”}}”

I am getting the following error
{"error":{"code":1510,"message":"Service Id not have a valid Requester Type"}}

#13

@IntegrationSupport I read some comments in the form that adding a new PHR service worked for them. I tried the same but the issue is still the same

image
image1828×1502 327 KB

#14

@IntegrationSupport any updates on the above? How can I fix this?

#15

@rahul260792 Error msg shows service ID not have a valid requester Type. Please add your PHR services from your backend to create a valid requester Type

#17

How can I do that? Please share the documentation @IntegrationSupport

#18

@rahul260792 Please check, we have fixed this from backend.

image
image796×103 7.79 KB