invalid_token location:["http.Authorization"]

60 views
Skip to first unread message
Assigned to desani...@gmail.com by eric.s...@cerner.com

chirag prajapati

unread,
May 20, 2021, 8:00:27 AM5/20/21
to Cerner FHIR Developers
We are facing issue in Put and Post request. It is not working from last month but it is working on our site. The issue is facing this problem at development time .

Each and every put and post request are failed in debug mode .

Below error we are getting 

{\"resourceType\":\"OperationOutcome\",\"issue\":[{\"severity\":\"error\",\"code\":\"login\",\"diagnostics\":\"Bearer realm=\\\"fhir-ehr-code.cerner.com\\\", error=\\\"invalid_token\\\"\",\"location\":[\"http.Authorization\"]}]}

Please help us to resolved this issue 

why it is working on web but not in development debug mode?

chirag prajapati

unread,
May 20, 2021, 9:07:52 AM5/20/21
to Cerner FHIR Developers
Hi Team,

This issue is coming for the development environment while running in the debug mode. 

But the same code is running well while we publish it on the Azure environment.

Fenil Desani (Cerner)

unread,
May 21, 2021, 11:42:49 AM5/21/21
to Cerner FHIR Developers
Hello,

Please provide X-Request-Id of the failure.

Thanks,
Fenil (Cerner)

chirag prajapati

unread,
May 24, 2021, 1:04:06 AM5/24/21
to Cerner FHIR Developers
Hi Team,

X-Request-Id = 641fd628-07cd-4e32-93c3-00f589dff00c
this is X-Request-Id , you can take it. and please help us as soon as possible .

Thanks and regards
Chirag Prajapati

chirag prajapati

unread,
May 24, 2021, 1:09:43 AM5/24/21
to Cerner FHIR Developers
Hi Team,

X-Request-Id =  e9ef15a7-1352-410d-864a-a181fc574671
this is X-Request-Id, you can take it. and please help us as soon as possible. Please take it this latest one .

Thanks and regards
Chirag Prajapati

Fenil Desani (Cerner)

unread,
May 24, 2021, 12:33:59 PM5/24/21
to Cerner FHIR Developers
For X-Request-Id: 641fd628-07cd-4e32-93c3-00f589dff00c, your token had expired. Make sure to use a valid token.
For X-Request-Id: e9ef15a7-1352-410d-864a-a181fc574671, there is a known issue where certain dstu2/r4 requests are failing. We expect the issue to be resolved by 5/25 EOB.

Reply all
Reply to author
Forward
0 new messages