Retrieving Client Alerts session information is not working properly. The "Login" call often fails with "Invalid ClientAlerts Auth Token" error, even though the client alerts token is valid.
Once you receive <ClientAlertsAuthToken> data in the response, it needs to be URL-encoded to escape special characters like "+", "=", space etc., before you can use it as a parameter in the "Login" request.
After you URL-encode the Client Alerts Auth Token, it can be safely sent over as a URL param in the "Login" call. It is always a good practice to URL-encode the parameters that are sent as URL params.
Token after encoding: AQAAAYL2WPAAAA0xfDEzMjg0NzczM3w3MzI2M3wxNjYzMTg2MjU5Nzg2fHVNY0V2VmhwTU5xTGV1YUZQMDVSWWQxeERmVXhjWmJlWGVEMDBLR3BaeFhBUU1VdS9QVTdHTzlhSXFXTWpPU0FjVDhyVjRyWnVHVE9WUGRxeFpHcHFnPT2lVnATfzq0HfP0hNgLD%2FOvolhnLw%3D%3D
Note that after URL encoding, the "/" and the "=" symbols in the token are encoded as %2F and %3D respectively
Step 3: Establish a Client Alerts session by passing in the Client Alerts token and retrieving session information