| Description |
This article describes and demonstrates steps to extract cookie and token information for API usage. |
| Scope | FortiADC. |
| Solution |
Security and Network admin often need to conduct API tasks. Sometimes, it can be troublesome to manually output the HTTP header and body data, and then copy the necessary information to continue communicating with API devices. For this demonstration, this article provides steps to extracting Cookie and Token information with a single line of command syntax.
The prerequisite needs to enable GUI admin access with HTTP, and HTTPS allowaccess services under network interface configuration in FortiADC.
To obtain cookie and token info, it is necessary to send an HTTP POST request to FortiADC.
Login FortiADC:
Example output: CURL command sends an HTTP request with user credentials and FortiADC response with a set of HTTP header and session information in JSON format.
Example output after filter. only interested cookie and token information were extracted from crowded information. Furthermore, HTTP header key values were updated.
For more information about the required HTTP header, refer to the related documentation on page 6.
Set-Cookie -> Cookie. Token -> Authorization: Bearer.
curl -H "Content-type: application/json" -H "Accept: application/json" -X POST -d '{"username":"admin","password":"xxxxxxxx"}' -s -k -i https://10.47.36.171/api/user/login | grep 'token\|Cookie' | tr -d '[:space:]' | cut -d ';' -f 1,6 | cut -d ',' -f 1,10 | sed -e 's/Set-/"/' -e 's/;.*,/" /' -e 's/"token":"/"Authorization: Bearer /' -e 's/}//'
Note: Provides command syntax was produced under a controlled environment. Thus, it is meant to serve as an example syntax for reference and not to be considered as a fully functional command syntax. Each environment setup may vary, verify with the staging environment before implementation.
Verification steps:
It will indicate that the HTTP request is successful by receiving the HTTP 200 OK response code.
It will indicate that the HTTP request failed by receiving an HTTP 401 Unauthorized response code. It is suggested to check user credentials.
Related document: |
