After upgrading SGOS on a ProxySG appliance or MACH5 edition appliance, scripts that send CLI commands to the system as POST method requests result in an error message, "Server requires a valid encrypted token in the request." The scripts worked prior to upgrading to SGOS 220.127.116.11 and later.
Server requires a valid encrypted token in the request.
Additional security mechanisms were implemented.
Your script must request an encrypted token from the appliance, and then include the token in subsequent HTTP requests that use the POST method.
When the encrypted token is passed in the header, it is identified by the label "X-Bluecoat-Enc-Token". Refer to the following example:
When the encrypted token is passed in the body, it can be part of a query string when Content-Type is "application/x-www-form-urlencoded", or it can be one of the multipart sections when Content-Type is "multipart/form-data".
Note: Some ProxySG Advanced URLs will accept only one of the specified content types.
Important: Standard formatting requires an empty line as the start of the body.
Important: Standard formatting requires an empty line after the