CounterPath Bria 4 Provisioning Guide - Enterprise Deployments - Manual (Page 10)

CounterPath Corporation
6
Your script must understand the names assigned to the macros.
For example a URL of:
might become this POST used to log in the user:
Note that “Username” and “Password” (with initial capitals) are always sent in a login POST; the URL does not
have to include macros for this data.
See “Script Samples” on page 21 for samples of some of the scripts that are mentioned in this manual.
See “Macros” on page 22 for a list of macros that Bria supports.
1.4.3 Communication Mechanism
All communications between Bria and the login server are performed over HTTP or HTTPS, as follows:
• Custom login uses POST.
• Remote update and remote upgrade use GET.
The remote provisioning mechanism does not support redirect.
If using HTTPS, you need a trusted certificate (not self-signed). Bria will only accept certificates whose
authenticity can be verified through the trust chain.
https://mycustomloginserver.com/login.php?platform=$platform$&lic=$license$
https://mycustomloginserver.com/login.php
--------------------------------------------------------------------------------------
Username=21187
Password=rosebud
platform=win32
lic=d3874ihfd8t23975v1iu5182ruity3iusapor236u545uye0r9qwjj