CounterPath Bria 3.0 Provisioning Guide – Retail Deployments User Manual

Page 18

Advertising
background image

CounterPath Corporation

14

Example that includes a license key being sent down to the computer:

where:

Success: this line is required.

LicenseKey: the license key for the computer. This data should be sent for a new deployment or if you want
to change the existing license key.

Settings: the username will be saved at shutdown.

##Memory##: the password will not be saved at shutdown.

The response must end with a CRLF.

License Key Verification by Bria

Bria next takes one of these actions, depending on the response received from the server:

If the response was a failure, then the Login dialog appears again. The process goes back to “Login
Procedure Is Invoked” on page 12
.

If the response was a success, then Bria checks if there is a license key in the response.

If the response includes a key, the key is validated and then Bria starts.

If the response includes a key, and validation fails, then the Enter License Key dialog appears.

If the response does not include a license key, then Bria checks if there is already a key stored on this
computer.

If yes, then Bria verifies that the key is valid and then starts.

If no, then the Enter License Key dialog appears. When the user enters the license key (obtained
outside of Bria, for example in an email sent to all new customers), the Bria verifies that the
entered license key is valid. If the key is valid, Bria starts.

[DATA]
Success=1
LicenseKey="e48jey45379ryeioo8a7e934q8dhfudufoladskiuwb"
[SETTINGS]
proxies:proxy:user_name="KPerera"
[##MEMORY##]
proxies:proxy0:password="rosebud"
<CRLF>

Advertising