Configuring HTTP POST Authentication
If you choose HTTP POST as your authentication method while Creating an Authentication Profile, specify values for the following fields to set up a Post call to authenticate to an external system.
Default Setting: Selecting the Default UI or Default API fields indicate the authentication profile that is currently set as a default UI or default API authentication type. However, there is no compulsion that only one authentication profile should be the default for both the UI & API authentications.
| Field | Description |
|---|---|
| Name | Type an authentication profile name. |
| Target URL | URL that identifies the HTTP device and port (typically, http://device:port-number/...) |
| HTTP Body | The template for the body of the HTTP POST request (typically a SOAP call). This must include tokens for user's input. |
| HTTP Headers | Valid HTTP request headers to pass as part of
the HTTP POST call. This is an optional field. Note: The Content-Type header is available only
for backward compatibility. You can leave the header
value as blank to not include it as part of your HTTP
POST call. |
| Response Text | Text that must be present in HTTP response to indicate if the authentication was successful (for example, <Authenticated>true</Authenticated> ). |
After specifying the above values, you must test your authentication method to check whether authentication succeeds. To test your authentication method:
- Under Test External Authentication, specify a valid login name and password.
- Click Test External Authentication.
Note that you cannot save your changes until the test succeeds.
