Stream: social
Topic: Epic access token using JWT
Pavan Patidar (Jul 21 2021 at 12:46):
Hi ,
I create application in Fhir. I want to access token from server. when i request it shows response like INVALID CLIENT.i create keypairs using openssl and created jwt by header type as jwt and Algorithm as RS384 and also payload as iss,sub,iat,aud,exp,jti and also signature publickey and private key as openssl created keys.it shows INVALID CLIENT. please help me for getting access token.
Below message i am receiving.
{
"error": "invalid_client",
"error_description": null
}
Josh Mandel (Jul 21 2021 at 12:48):
Your subject line mentions Epic; and whether it supports fhir backend services? You can look in the server's documentation or .well-known/smart-configuration file for information about supported client authentication methods.
Pavan Patidar (Jul 21 2021 at 12:53):
Yes i followed the exact steps that are mentioned in the document.
Lloyd McKenzie (Jul 21 2021 at 14:44):
@Pavan Patidar Have you reached out to open@epic.com?
Pavan Patidar (Jul 22 2021 at 09:57):
Yes i have sent an email regarding the same.
Lloyd McKenzie (Jul 22 2021 at 14:23):
If it's been over a couple of business days with no response, holler and I can try to draw some attention to your question from the Epic folks
Rom Mesa (Jul 23 2021 at 01:56):
@Pavan Patidar , I encountered the same issue initially and figured my problem was with the exp value I used (have to be now + 5min only). I also removed the nbf and iat values and everything's working now.
Pavan Patidar (Jul 23 2021 at 06:21):
Thanks @Rom Mesa
It worked, You saved my time.
Gowtham (Jul 26 2021 at 12:28):
Hi ,
Iam want to access patient.read api in fhir
using Access token Iam going to access only patient.search .I not able to access patient.read and other API
please help me, In the body field will we set scope for what are all api Iam going to access
if yes please say the format for scope for accessing patient.read and observation.read Api
David Pyke (Jul 26 2021 at 12:59):
This channel is for social discussions. Technical discussions should be in #implementers
David Pyke (Jul 26 2021 at 12:59):
for SMART questions in particular, ask in #smart
Last updated: Apr 12 2022 at 19:14 UTC
