FHIR Chat · Cambia Healthsparq server · CARIN IG for Blue Button®

Stream: CARIN IG for Blue Button®

Topic: Cambia Healthsparq server

Michele Mottini (Sep 14 2019 at 15:17):

I got the auth token, now I try to GET a Patient but fails with
{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "Forbidden: Token not present"
}
]
}

Michele Mottini (Sep 14 2019 at 15:17):

I have put the token in the Authorization header as a Bearer token...

Michele Mottini (Sep 14 2019 at 15:28):

@Amol Vyas ^

Paul Church (Sep 14 2019 at 15:28):

the token goes in the subject-token header

Michele Mottini (Sep 14 2019 at 15:29):

That's wrong

Paul Church (Sep 14 2019 at 15:30):

I agree that it's wrong, but I was able to get the data that way

Michele Mottini (Sep 14 2019 at 15:31):

OK - I'd like someone from Cambia to acknowledge that it is a problem and that would be fixed

Clay Graham (Sep 14 2019 at 15:37):

Hey Michele

Douglas DeShazo (Sep 14 2019 at 15:37):

Is there an EOB resource that we can use for this track? I don't find it the track information or the CI build.

Clay Graham (Sep 14 2019 at 15:37):

You just need to re-authenticate

Clay Graham (Sep 14 2019 at 15:39):

If you refresh the token call it should give you a new token

Clay Graham (Sep 14 2019 at 15:40):

The auth pattern is a JWT pattern until our OAUTH2 connector is up EOY

Clay Graham (Sep 14 2019 at 15:41):

curl -X POST \
  https://api-gateway.uat2.healthsparq.com/healthsparq-api-token-service/v1/token \
  -H 'Accept: */*' \
  -H 'Accept-Encoding: gzip, deflate' \
  -H 'Authorization: Basic OGVmNWY4NGI5M2MyNDM2ZGFmMjgwZTgwODcwZTUzYmM6MDEzZWEzM2UxNmJiNGVmNGIyNmE2NGU1ZGNiM2YwYTU=' \
  -H 'Cache-Control: no-cache' \
  -H 'Connection: keep-alive' \
  -H 'Content-Length: ' \
  -H 'Cookie: dtCookie=29$98288D839504848187D99DCD234D551B; visid_incap_2033455=Hrwyv1ONTvWoA6jWAh5kYeQM41wAAAAAQUIPAAAAAABJnDsXhSJsPhW/D7mz4KOL; nlbi_2033455=E4ArIYVIRnZP8G0teIqUmQAAAABBM6YvpP/Fk+s7OrT6nti0; incap_ses_542_2033455=/rfiK71sxHFphGwffpOFB+rYel0AAAAA0yzdTKjLJRa/h06k6BoKTQ==; incap_ses_526_2033455=QNi7cpwDDggefsQuF9lMB7f8fF0AAAAAabY5/LY2lmhAYeaJvxxESA==' \
  -H 'Host: api-gateway.uat2.healthsparq.com' \
  -H 'Postman-Token: b4e5cc53-c3bc-4949-864b-74413beebd02,a8b6e125-0069-454a-8224-2ecdb8a9f24b' \
  -H 'User-Agent: PostmanRuntime/7.15.2' \
  -H 'cache-control: no-cache'

Michele Mottini (Sep 14 2019 at 15:49):

@Clay Graham I don't understand - the token was not expired (?), the server expects it in the wrong place

Clay Graham (Sep 14 2019 at 15:52):

It may have, are you on the HL7 floor? Can you come to table 4?

Michele Mottini (Sep 14 2019 at 16:16):

On my way

Last updated: Apr 12 2022 at 19:14 UTC