REST V2 Connector

Back Next

OAuth 2.0 authorization code authentication

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 the error codes

400

401

, and

403

are returned in the response, Informatica redirect URL, which is outside the customer firewall, tries to connect to the endpoint and retrieves a new access token.

The following table describes the basic connection properties for OAuth 2.0 authorization code authentication:

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 has defined custom scopes. Enter scope attributes, each separated by a space. For example, root_readonly root_readwrite manage_app_users
Access Token Parameters	Additional parameters to use with the access token URL. Define the parameters in the JSON format. For example, [{"Name":"resource","Value":"https://<serverName>"}]
Authorization Code Parameters	Additional parameters to use with the authorization token URL. Define the parameters in the 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 .
Generate Access Token	Generates an access token and refreshes the token based on the information provided in the above fields.
Access Token	The access token value. Enter the access token value or click Generate Access Token to populate the access token value. To pass the generate access token call through a proxy server, you must configure an unauthenticated proxy server in the Secure Agent properties. The proxy configured in the connection configuration does not apply to the generate access token call.
Refresh Token	The refresh token value. 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 fetches a new access token with the help of refresh token. If the refresh token expires, you must either provide a valid refresh token or regenerate a new refresh token by clicking Generate Access Token .
Swagger File Path	The path of the Swagger file or OpenAPI file. You can specify one of the following file paths: Path and file name of the Swagger or OpenAPI file on the Secure Agent machine. The URL on which the Swagger or OpenAPI file is hosted. The hosted URL must return the content of the file without prompting for further authentication and redirection. For example, the path of the swagger file can be: C:\swagger\sampleSwagger.json The user must have the read permission for the folder and the file.

Rename Saved Search

Table of Contents

REST V2 Connector

REST V2 Connector

OAuth 2.0 authorization code authentication

OAuth 2.0 authorization code authentication