Session Management

Irrespective as to whether ESCWA has been restricted or not, all clients must use a session to perform their actions. This topic details how you can establish a session.

If ESCWA is secured, a request should first be sent to the endpoint /logon with your credentials.
If ESCWA is unsecured, a request should first be sent to the endpoint /validate.

In either case, the response will have a set-cookie header containing ESAdmin-Cookie. This cookie should be sent with every subsequent request.

If you need to logon to any other resources, such as directory severs, regions, or ES for .NET then the session information will be added to your ESCWA session and so only the ESAdmin-Cookie is required.

Once your script is complete it should finish with a request to the /logoff endpoint to clean up the session. This is to reduce the risk of reaching the session limit and minimize resource usage.