CounterPath Bria Professional 2.5 Provisioning Guide - Manual (Page 17)

Provisioning Bria Professional OEM Edition
13
might become this POST used to log in the user:
where:
• “Username” and “Password” (with initial capitals) are always sent in a login POST; the URL does not have
to include macros for this data.
• platform and lic are macros used by the login script; see “Use of Scripts and Macros” on page 5.
License Key Management
You should set up Bria Professional to include the license key in the data sent to the login server. There are two
ways to send this data:
• Include one of the license macros in the URL. See page 22.
• Set the setting feature:custom_login:always_include_license_in_post to true.
Verification Step
Your login server should perform any suitable verification on the sent data, according to your business rules.
Typically, this verification will include one of the following checks on the license key:
• For a new deployment (no license key was included in the query), determine that the query is valid, and if
so, obtain a license key to send back to the user.
• For an existing deployment (the license key was included in the query), do nothing.
Response Step: Failure
If there is a problem with any of the data, the login server should return failure data in the following format:
Response Step: Pass
If the server can handle the request, it should return a success message and the account credentials. It can also
return other settings that can be specified only at login.
Example with a license key passed in the SETTINGS section:
https://mycustomloginserver.com/login.php
--------------------------------------------------------------------------------------
Username=21187
Password=rosebud
platform=win32
lic=d3874ihfd8t23975v1iu5182ruity3iusapor236u545uye0r9qwjj
[DATA]
Success=0
Failure="<message> "
<CRLF>
[DATA]
Success=1
[SETTINGS]
proxies:proxy0:user_name="KPereira"
system:license:key=”e48jey45379ryeioo8a7e934q8dhfudufoladskiuwb”
[##MEMORY##]
proxies:proxy0:password="rosebud"
<CRLF>