Cookie-based Authentication
Function:
The tool Cookie-based Authentication enables you to use HTTP cookie-based authentication to a Web application. The server sends a cookie which is stored on the client side and is used for further requests to this server.
The tool can be found under the category Authentication of REST function package tools.
Parameters:
| Parameter Name | I/O | Type | Description |
|---|---|---|---|
| Login Path [M] | I | String | The URL to the login script of the Web application |
| Credential Structure [M] | I | File | The File Descriptor of JSON structure containing the user credentials as expected by the Web application |
| Realm [O] | I | String | Realm enables a mapping between client application and Web application. It is only relevant if an AWM application addresses different Web applications. |
| Cookie Name * [O] | I | String | Name of the authentication cookie to be used for the specific Web application if known. The cookie name can be found in the REST API documentation of the server application. |
Relationship: REST Tool Has Request Header
The relationship REST Tool Has Request Header enables you to specify a name/value pair to be sent in the HTTP request header.
If specified in an authentication request the name/value pair is sent with every HTTP request for the signed in session.
| Attribute | Type | Description |
|---|---|---|
| Name | String | Name of the HTTP header field |
| Value | String | Value of the HTTP header field |
Example:
The example shows a tool to authenticate with the Micro Focus Enterprise Server. The authentication to a Micro Focus Enterprise Server needs three special header fields:
The file descriptor describing the credential structure is modelled as follows:
