Configuring HTTP POST Authentication
HTTP POST authentication lets the platform verify user credentials by sending an HTTP POST request to an external service. The service validates the credentials and returns a response indicating success or failure. During configuration, administrators must specify the endpoint URL, request body, headers, and the encoding format used when sending the HTTP POST request while Creating an Authentication Profile.
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 | Specifies the name of the authentication profile. |
| Target URL | Specifies the endpoint URL where Infinite Blue sends the HTTP POST request to validate user credentials. (typically, http://device:port-number/...) |
| Encoding |
Specifies the format used to send the HTTP POST request body. Available options include:
|
| HTTP Body | Defines the body of the HTTP POST request sent to the authentication service. This must include tokens for user's input. |
| HTTP Headers | Specifies 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.