AudioCodes Mediant 500 E-SBC, Руководство пользователя

Страница: 589 / 920

User's Manual 40. Automatic Update Mechanism
Version 6.8 589 Mediant 500 E-SBC
40.2.4 Access Authentication with HTTP Server
You can configure the device to authenticate itself with the HTTP/S server. The device
authenticates itself by providing the HTTP/S server with its authentication username and
password. You can configure one of the following HTTP authentication schemes:

Basic Access Authentication: The device provides its username and password to
the HTTP server. The username and password is configured in the URL that you
define for downloading the file:
•
ini file:
AutoCmpFileUrl = 'https://<username>:<password>@<IP address
or domain name>/<file name>'
•
CLI:
# configure system
(config-system)# automatic update
(automatic-update)# auto-firmware
https://<username>:<password>@<IP address or domain
name>/<file name>

Digest Access Authentication: The authentication username and password is
negotiated between the device and HTTP/S server, using digest MD5 cryptographic
hashing. This method is safer than basic access authentication. The digest
authentication username and password are configured using the
AUPDDigestUsername and AUPDDigestPassword parameters, respectively.
40.2.5 Querying Provisioning Server for Updated Files
Each time the Automatic Update feature is triggered, for each file and its configured URL
the device does the following:
1. If you have configured the device to authenticate itself to the HTTP/S server for secure
access, the device sends the access authentication username and password to the
HTTP/S server (for more information, see Access Authentication with HTTP Server on
page
589 ). If authentication succeeds, Step 2 occurs.
2. The device establishes an HTTP/S connection with the URL host (provisioning
server). If the connection is HTTPS, the device verifies the certificate of the
provisioning server, and presents its own certificate if requested by the server.
3. The device queries the provisioning server for the requested file by sending an HTTP
Get request. This request contains the HTTP User-Agent Header, which identifies the
device to the provisioning server. By default, the header includes the device's model
name, MAC address, and currently installed software and configuration versions.
Based on its own dynamic applications for logic decision making, the provisioning
server uses this information to check if it has relevant files available for the device and
determines which files must be downloaded (working in conjunction with the HTTP If-
Modified-Since header, described further on in this section).
You can configure the information that is sent in the User-Agent header, using the
AupdHttpUserAgent parameter or CLI command, configure system > http-user-agent.
The information can include any user-defined string value or the following supported
string variable tags (case-sensitive):
•
<NAME> - product name, according to the installed Software License Key
•
<MAC> - device's MAC address
•
<VER> - software version currently installed on the device, e.g., "6.80.200.001"
•
<CONF> - configuration version, as configured in the ini file parameter,
INIFileVersion or CLI command, configuration-version
The device automatically populates these tag variables with actual values in the sent
header. By default, the device sends the following in the User-Agent header: