Connections > FHIR connection properties > OAuth 2.0 authorization code authentication
  

OAuth 2.0 authorization code authentication

Configure authentication properties in the FHIR connection to use an OAuth 2.0 authorization code.
To use authorization code authentication, register the following Informatica redirect URL in your application:
https://<Informatica cloud hosting facility for your
organization>/ma/proxy/oauthcallback
If the access token expires and you receive error code 400, 401, or 403 in the response, the Informatica redirect URL tries to connect to the endpoint and retrieve a new access token. Note that the Informatica redirect URL is usually outside the organization firewall.
The following table describes the authentication properties for a FHIR connection that uses an OAuth 2.0 authorization code:
Property
Description
Authorization Token URL
Authorization server URL configured in your application.
Access Token URL
Access token URL configured in your application.
Client ID
Client ID of your application.
Client Secret
Client secret of your application.
Scope
Specifies access control if the API endpoint defines custom scopes. Separate scope attributes using a space.
For example: root_readonly root_readwrite manage_app_users
Access Token Parameters
Additional parameters to use with the access token URL. Define parameters in JSON format.
For example: [{"Name":"resource","Value":"https://<serverName>"}]
Authorization Code Parameters
Additional parameters to use with the authorization token URL. Define parameters in JSON format.
For example: [{"Name":"max_age","Value":60},{"Name":"state","Value":"test"}]
Client Authentication
Select an option to send the client ID and client secret for authorization either in the request body or in the request header.
Default is Send Client Credentials in Body.
Access Token
Enter the access token value or click Generate Access Token to populate the access token value.
To generate the access token through a proxy server, configure an unauthenticated proxy server on the Secure Agent. The FHIR connection-level proxy configuration doesn't apply when generating the access token.
Refresh Token
Enter the refresh token value or click Generate Access Token to populate the refresh token value. If the access token is not valid or expires, the Secure Agent generates a new access token through the refresh token.
If the refresh token expires, you must either enter a valid refresh token or generate a new refresh token by clicking Generate Access Token.