DEPRECATED: How to Add a Reporting Token to a Container

Warning: This article refers to deprecated functionality which is retained for those customers running earlier releases of our products.
For current versions of Cloudhouse Alchemy Compatibility Packages, please refer to Licensing and Usage Reporting for the most up-to-date information.

Containers require a reporting token to report usage events to https://containers.cloudhouse.com.

If you dont have an HTTPS Reporting token for your customer already, one can be requested from support@cloudhouse.com.
You will receive your HTTPS Usage Reporting token via secure email, open the link in the email and provide your email address to download the file.
The token file is a text file, named usage-customername.token, and formatted using JSON so that you view the contents of the file in a text editor. If the editor supports JSON then formatting will applied.
```
{
   "token": "%Token%",
   "clientid": "%ClientId%",
   "deviceid": "%DeviceId%",
   "description": "Usage token is allocated to %Partner% to report Container usage on behalf of %Customer%."
}
```
Once you have created the Container, copy the .token file into the Container's root folder OR use the Container Editor - refer to Updating, Editing and Maintaining a Cloudhouse Compatibility Container‍.

Check that chmetadata.json contains the following entries, if not add them.

"AuthUrl": "https://auth.cloudhouse.com/oauth/token",
"UsageReportingUrl": "https://containers.cloudhouse.com/api/UsageEvents"

The token will be encrypted when the Container is deployed, the extension will change to .stoken and HTTPS reporting will be used to send usage data to Cloudhouse.

Embedded content from https://www.youtube.com/watch?v=0syalyE7HE4

Applies To

Container version must be 4.5.249.480, or later.