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

Bria 4 Provisioning Guide – Enterprise Deployments
7
1.4.4 Data Format
All the data included in the GET or POST response is in a specific format. This format is similar to that of
Microsoft
®
Windows
®
.ini files.
The information is organized into three portions, which must appear in this order:
• [DATA]
• [SETTINGS]
• [##MEMORY##]
Example
[DATA]
This section contains the response to requests:
Success=, a boolean. This data is required.
Failure=, which is optional if the success is 0. For login, the string you enter here will be displayed
in the Login dialog.
[SETTINGS]
This section contains settings to be written to persistent memory. The values will be used immediately.
At shutdown, these settings will be written to the local settings file on the Bria computer.
[##MEMORY##]
This section contains settings to be written to non-persistent memory. The values will be used immediately, but
only for the current session.
At shutdown, these settings will not be written to the local settings file.
CRLF
The response must end with a CRLF. If this is missing, the last line of the response is ignored.
Handling and Encryption of Passwords
All “password” settings in any domain/section are handled as follows:
• Bria does not interpret passwords in any way, so the value the login server passes to Bria can be encrypted.
• Bria encrypts the value before storing it, regardless of whether or not it is already encrypted. When a stored
value is read in order to pass it to the login server, it is first decrypted.
• When a password that the user has entered into a dialog is then passed to the login server, Bria does not
encrypt the value.
[DATA]
Success=1
[SETTINGS]
proxies:proxy0:display_name="Kokila Perera"
proxies:proxy0:enabled="1"
proxies:proxy0:username="6045550008"
proxies:proxy0:password="dfher43d89dhferuieo98375uy8”
proxies:proxy0:domain="acphone.com"