Getting 400 error with "invalid client" response message - regarding
59 views
Skip to first unread message
Ponnumani G
Apr 25, 2024, 9:09:12 AMApr 25
to SMART on FHIR
Hi Team,
I am following EPIC documentation of Backend OAuth 2.0 and based on that trying to create JWT token and access token. But I am getting 400 error with "invalid client" response message.
I am following EPIC documentation of Backend OAuth 2.0 and based on that trying to create JWT token and access token. But I am getting 400 error with "invalid client" response message.
Header :
{
"alg": "RS384",
"typ": "JWT",
"kid": "0115A8BCC1D9AEE8290DC65F676FEBF4C9F28A81"
}
KID value, I am taking from uploaded public key place
payload:
{
"iss": "bab47eed-6485-491c-8f6f-3199b8fa2cbb", //
Non-Production Client ID
"sub": "bab47eed-6485-491c-8f6f-3199b8fa2cbb", //
Non-Production Client ID
"aud": "https://fhir.epic.com/interconnect-fhir-oauth/oauth2/token",
"jti": "System_1714049232",
"exp": 1714049232,
"nbf": 1714049232,
"iat": 1714049232
}
private key:
private key:
-----BEGIN RSA PRIVATE KEY-----
MIIEowIBAAKCAQEAx2prm6jUsJbzExxB1FpTAFKL3xT/dxgnRyLL0oWaIvx+m0Hx
aZJ9xOKIr2JZOFc0K07+5R3UyR6CzHvNnQeByrP6fc4KrErmLtS+ojl/8E601VA8
bdcnEVicAzEeVlD1X2Frp5pmCrgA+z4lf8NL9kzIBelwkV84ooTzQrTGv4rt/leC
RqGfWWGzWYwptugdTlOaI2q85KBSncTTnysePz6mnQH4v0lh2nTWFKio3FWX+J1E
UnrURzakilXj1qQqZh8KvuXFqHzGs1lN79EzUZ5qUG5GdwCwKEcliAKLKCgk6UUq
RLAUZfmXxkzkcP67IqqKIfQdjWRYlbCqDDlt0wIDAQABAoIBADqznRGpVVLWXJ+X
hdlY7W3+3qXArKMGPSm3mIBUS9dYtHxHoSUOtm8qsEnQjasEIJtPGcGgUm8RyDch
iplbCF3/NRGrgYDOW4wVnDhs7Lh0ss7IW8GJwDpe9y4JW4DVPCXjq6kezkMBf2h2
FtvRRZ8vYwI6gaSJf0Z4FJPiW08utUrxszJD+PB5g5YqpEPX74gzs2umW5UUMmS+
gz6XidAkiWanoShQZX1Jb89TLjNxTMCTvifRBINuRPson9hx6E45dNRmKkaIK31C
Zh4AM6bhTdHp9cZttUEiCl641LqqLcxhhr+yUHCOaARGqkiIBwAvA08JYy98Z5yh
gwBz2IECgYEA7Ra9nkL7wQw4uamq8fpoInbwrMa7GsMpHb5G1CHesrKe4CWSUxJJ
ToZNkZ44I9f40C0PZXST9MBJ5z8eeTo07E9cz5SsRckqjx2tvUPem0JiO75cA35M
9Ve7KN0cUFh6ZNqkP2M4ncSodJI8GsO//rx9cBy240li6uJv3L7OR3ECgYEA11Jo
0TmIvRFp4+A0hPyCsfZJ4QDV92+naMWT3eAzah7TWPmtpVupo5M5uXBLtzHpK/u+
S6GrDHqgaAetviSqQaS4vhYRY62bVUo4SStA3RMLSXBefLdeYgdjBD9sytI9sb6z
WPNJfsQm7p6c1E2efySmZNWr0JLi64lpdyEPT4MCgYAQaNqG8avrGKV0dEHYrbQ3
bnQKAVdB6vAVlu3gENgRFjvY18Dg7wsT3EfSJFlOYcxe3D+Mjh0Pe5+h2cSKL3Uq
RfPuiiPCUMIZVbyItQHbTSTvbaWAuGUrNf9GPMeQ6A7QnDFyEbQBd3MRXm26jIHl
Z7Zm5BXkdVfbWgDUDoDIgQKBgQDQqYX2K8E9J+Dr+dwre+DTwQ77QyoW7VbYi4+u
FpT8o/7AXMVQV7HfWM85y380euOxwfY5qOPv5e4IolhWyYVMs+psG0qixByh3JkL
HyVumAP6GTEXv0Nx0CK+fRBaxL8QvvNiofF5LXFlEMR+YPHV2Jh/YylrqMzK4JEZ
5ynFLQKBgGXXN/nuYI4OMcphQKJLUwknm3iIy+NNQefYJclpI2QRhCbbcWC3mABF
6kFeKsySNyXWMq1gDoI0TFmQm84BuGvkbBFUrviTwzlbVSgtKHUxYE57kBEXdedv
4vxkriPAIcTNrxIqhs/0CTrxYfdho9zF5rZ6dJmu7glELCdNkjwy
-----END RSA PRIVATE KEY-----
Shall you any one check this issue and guide me to create valid JWT token..
Thanks,
MIIEowIBAAKCAQEAx2prm6jUsJbzExxB1FpTAFKL3xT/dxgnRyLL0oWaIvx+m0Hx
aZJ9xOKIr2JZOFc0K07+5R3UyR6CzHvNnQeByrP6fc4KrErmLtS+ojl/8E601VA8
bdcnEVicAzEeVlD1X2Frp5pmCrgA+z4lf8NL9kzIBelwkV84ooTzQrTGv4rt/leC
RqGfWWGzWYwptugdTlOaI2q85KBSncTTnysePz6mnQH4v0lh2nTWFKio3FWX+J1E
UnrURzakilXj1qQqZh8KvuXFqHzGs1lN79EzUZ5qUG5GdwCwKEcliAKLKCgk6UUq
RLAUZfmXxkzkcP67IqqKIfQdjWRYlbCqDDlt0wIDAQABAoIBADqznRGpVVLWXJ+X
hdlY7W3+3qXArKMGPSm3mIBUS9dYtHxHoSUOtm8qsEnQjasEIJtPGcGgUm8RyDch
iplbCF3/NRGrgYDOW4wVnDhs7Lh0ss7IW8GJwDpe9y4JW4DVPCXjq6kezkMBf2h2
FtvRRZ8vYwI6gaSJf0Z4FJPiW08utUrxszJD+PB5g5YqpEPX74gzs2umW5UUMmS+
gz6XidAkiWanoShQZX1Jb89TLjNxTMCTvifRBINuRPson9hx6E45dNRmKkaIK31C
Zh4AM6bhTdHp9cZttUEiCl641LqqLcxhhr+yUHCOaARGqkiIBwAvA08JYy98Z5yh
gwBz2IECgYEA7Ra9nkL7wQw4uamq8fpoInbwrMa7GsMpHb5G1CHesrKe4CWSUxJJ
ToZNkZ44I9f40C0PZXST9MBJ5z8eeTo07E9cz5SsRckqjx2tvUPem0JiO75cA35M
9Ve7KN0cUFh6ZNqkP2M4ncSodJI8GsO//rx9cBy240li6uJv3L7OR3ECgYEA11Jo
0TmIvRFp4+A0hPyCsfZJ4QDV92+naMWT3eAzah7TWPmtpVupo5M5uXBLtzHpK/u+
S6GrDHqgaAetviSqQaS4vhYRY62bVUo4SStA3RMLSXBefLdeYgdjBD9sytI9sb6z
WPNJfsQm7p6c1E2efySmZNWr0JLi64lpdyEPT4MCgYAQaNqG8avrGKV0dEHYrbQ3
bnQKAVdB6vAVlu3gENgRFjvY18Dg7wsT3EfSJFlOYcxe3D+Mjh0Pe5+h2cSKL3Uq
RfPuiiPCUMIZVbyItQHbTSTvbaWAuGUrNf9GPMeQ6A7QnDFyEbQBd3MRXm26jIHl
Z7Zm5BXkdVfbWgDUDoDIgQKBgQDQqYX2K8E9J+Dr+dwre+DTwQ77QyoW7VbYi4+u
FpT8o/7AXMVQV7HfWM85y380euOxwfY5qOPv5e4IolhWyYVMs+psG0qixByh3JkL
HyVumAP6GTEXv0Nx0CK+fRBaxL8QvvNiofF5LXFlEMR+YPHV2Jh/YylrqMzK4JEZ
5ynFLQKBgGXXN/nuYI4OMcphQKJLUwknm3iIy+NNQefYJclpI2QRhCbbcWC3mABF
6kFeKsySNyXWMq1gDoI0TFmQm84BuGvkbBFUrviTwzlbVSgtKHUxYE57kBEXdedv
4vxkriPAIcTNrxIqhs/0CTrxYfdho9zF5rZ6dJmu7glELCdNkjwy
-----END RSA PRIVATE KEY-----
Shall you any one check this issue and guide me to create valid JWT token..
Thanks,
Ponnumani
Abigail Watson
May 3, 2024, 12:40:22 PMMay 3
to SMART on FHIR
I've been struggling with this for the past couple of weeks also. Debugging message is very poor; and it seems to be a 48hr+ wait time for clients to become activated.
Reply all
Reply to author
Forward
0 new messages