cancel
Showing results for 
Search instead for 
Did you mean: 

Cerner FHIR API Call using OAuth 2.0 (Client Credentials) - Get Token

SrikanthP
Level 2
Hi all, 
I am facing a challenge is getting a token from Cerner FHIR. I have followed the instructions as per Blue Prism recommendation and still facing some issues with the config. I have attached the settings within Blue prism. Any help would be greatly appreciated.

------------------------------
Srikanth Parasa
------------------------------
1 BEST ANSWER

Helpful Answers

@Srikanth P,

If you're going to use the Web API feature you can make use of the Common Authentication section, within the Web API service definition, to configure your authentication needs. You don't have to define your own action to get the token. You simply select the type of OAuth authentication the service uses (ex. OAuth Client Credential or OAuth JWT Bearer Token), select a credential from Credential Manager that contains the necessary client ID and client secret or issues and private key information and Blue Prism will handle the negotiation with the REST service for you whenever you can one of the other actions on the Web API.

Cheers,


------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

View answer in original post

3 REPLIES 3

bruce.liu
Staff
Staff
Hi Srikanth,

It seems to me that you are trying to retrieve the access token by defining the OAuth2.0 request and response manually. It is doable, but please consider the following:

  • You do not need Content-Type header under Common Headers as well as Request > Headers. You just need one of them.
  • You should set Common Authentication section to use "None", since you have opted to manually define the OAuth 2.0 request.
Unfortunately I do not have the access myself to test this for you. But the above are two most obvious issues I can find.

That aside, have you considered using Common Authentication alone to achieve what you need? It is not entirely necessary to manually craft OAuth 2.0 request and response. The easiest way to get OAuth 2.0 to work is by using Common Authentication section. In this way, you do not expose access token, it is automatically done for you by the calling requests defined under the Web API Service section. Neither do you need to worry about any possible access token expiration or renewral, which in your case, will require a lot of manual workaround if this is applicable.

Hope this helps.

------------------------------
Bruce Liu
Senior Product Consultant, Professional Services
Blue Prism
Australia/Sydney
------------------------------

Hi Bruce,
Thanks for your response. I have tried the suggestion you made and it did not help me much. I am keen to know what you mean by "have you considered using Common Authentication alone" this and can you please provide more details on how I can accomplish that? That would be really helpful. 

Thanks,
Srikanth.


------------------------------
Srikanth P
------------------------------

@Srikanth P,

If you're going to use the Web API feature you can make use of the Common Authentication section, within the Web API service definition, to configure your authentication needs. You don't have to define your own action to get the token. You simply select the type of OAuth authentication the service uses (ex. OAuth Client Credential or OAuth JWT Bearer Token), select a credential from Credential Manager that contains the necessary client ID and client secret or issues and private key information and Blue Prism will handle the negotiation with the REST service for you whenever you can one of the other actions on the Web API.

Cheers,


------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------