To open the HTTP/2 Client agent configuration dialog from a workflow configuration, you can do either one of the following:
...
| Setting | Description | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Use OpenAPI Profile | Select this option if you want the agent to use the OpenAPI profile(s). | ||||||||||
| OpenAPI Profile | Browse and select the profile to be used. This field is enabled when the Use OpenAPI Profile option is selected. Click Browse to search for the available OpenAPI profiles.
| ||||||||||
| Enable Validation | Select this option if you want to validate the OpenAPI profile.
|
Authentication Tab
The Authentication tab contains settings for the following Authentication types:
...
| Setting | Description |
|---|---|
| Grant Type | Select the grant type:
|
| Client ID | Enter the unique client identifier issued by the authorization server. |
| Client Secret | Enter the client secret. |
| Username | Enter the resource owner username, this can be the end-user granting access to a protected resource. This field is required when you have selected Resource Owner Password Credentials from the drop-down list Grant Type. |
| Password | Enter the password associated with the username. This field is required when you have selected Resource Owner Password Credentials from the drop-down list Grant Type. |
Access Token URI | Enter the URI where the access token can be obtained. |
Token expiration override (sec) | Enter a time in seconds when you would like to refresh the access token prior to the expiration. This allows the application to obtain a new access token without the user's interaction. |
| Additional Parameters | Some authentication servers may require additional parameters in the body of the token requests. To add a parameter, click the Add button and then enter the name of the parameter in the Key field and the value of the parameter in the Value field. Do not use escape characters in the value field, these will be added automatically by the HTTP2 Client agent. For instance, "https://example.com/" will be sent as "https%3A%2F%2example.com%2F". |
| Note | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
If an agent is configured on the Authentication Tab to use OAuth 2.0, an additional step may be required if the token needs to be obtained via HTTPS protocol. The HTTP/2 Client internally uses the Java built-in HTTP Client to obtain a token. If a certificate is required to contact the authentication server, the proper certificate has to be put into the default certificates file for the respective JDK distribution used.
|
...