I encountered 401 before and I go to
System > Security Management > View Audit Database
and check that the token passed the authentication server, so at that moment I suspect it doesn't pass the fhir server. After asking the support, we found out that, when checking out the token, we need to add the correct audience and scope (user/*.read user/*.write) to make it work.
**example**
Access Token URL : https://www.somewhere.com/oauth2/token?aud=https://www.somewhere.com/cs…
Scope : user/*.read user/*.write
with corresponding client_id and client_secret
and check out the token. after that, it can pass the fhir server authentication
- Log in to post comments
.png)