Hi, now I would like to continuous on the topic that we talk about previously
Using Postman for testing the OAuth2.0 of the InterSystems FHIR repository - Part1
.png)
Question 1: Where is my client_id and client_secret come form?
Short answer: Authentication Server.
If you don't have an Authentication Server, you may set up one as following
.png)
Provide the hostname (the host must support Https), at least 1 grand type (we choose client credential here), and SSL/TSL configuration
.png)
Input the scopes (here we input user/*.read and user/*.write, which is based on the scope support by the FHIR server (resource server)). Just in case if there is some scope we missed, check the Allow unsupported scope.
.png)
JWT setting choose RS256 (this is just an example, you may choose the one that fit your architecture)
.png)
Change the Generate token class to %OAuth2.Server.JWT. And update the namespace if needed.
.png)
Save the setting
Question 2: How to check out client_id and client_secret come form Authentication Server?
Short answer: Setup an OAuth2.0 Client (if you don't have) and created a client
Below are the steps for setting up an OAuth 2.0 Client.
.png)
Click Create Server Description
.png)
Input the Issuer end point and SSL/TLS configuration here
and click Discover and Save
.png)
You can find the related information in the OAuth2.0 Server configuration page
.png)
After the Discover and Save, you may see something similar to below. We may need to take a look at the token endpoint, which we need it for checking out a token
.png)
After the configuration above, now, it's time for us to create a client call postman 😁
Click on the OAuth 2.0 Client button
.png)
Click on the Client Configurations
.png)
Click Create Client Configuration
.png)
Input the Application name and Client name, choose the Client type confidential, input the Hostname for the Client redirect URL, choose the Required grant types Client credentials
Click Dynamic Registration and Save
.png)
You may see something similar as following.
Now, it's time to check out our client_id and client_secret😁😁
Click on the Client Credential tab
.png)
You can copy you client_id and client_secret here 😉
.png)
Question 3: How to add my FHIR server as resource server and related to Authentication Server?
Short answer: Setup an OAuth2.0 Client (if you don't have) and create a resource server. Then apply the resource server to the FHIR server setting
To create a resource server
Click on the Client Configurations
.png)
Click Create Client Configuration
Input the Application name and Client name, choose the Client Type Resource Server
Click Dynamic Registration and Save
.png)
Now the Resource Server is setup, then we should apply it to the FHIR server
Go to Health
.png)
Then, FHIR Server Management
.png)
Then choose the FHIR server to Edit
.png)
In the FHIR Server Authorization Setting tab, choose the OAuth Client Name from the list and Save
.png)
Yeah!! I think that all we need to setup our InterSystems FHIR server with OAuth feature😁
For testing with Postman, you may refer back to the pervious article
Using Postman for testing the OAuth2.0 of the InterSystems FHIR repository - Part1
Thank you very much for reading!😆😀
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
をクリックすると、メニューがアイコンから字に変わります。.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
ボタンをクリックします。.png)
.png)
.png)
.png)