41-001343-01 Rev 02, Release 3.2.2
5-339
Authentication Support for HTTP/HTTPS Download Methods, used with Broadsoft
Client Management System (CMS)
The IP phones support HTTP/HTTPS digest authentication as defined in
RFC 2617. (The HTTP client supports digest authentication; the HTTP server does not; the HTTP
server supports basic authentication). This feature allows the phones to interoperate with
Broadsoft’s CMS phone configuration tool.
Using the configuration files, you can enable/disable the following parameter to display a LOG IN
softkey which allows the HTTP/HTTPS server to perform digest authentication:
•
http digest force login
- specifies whether or not to display the LOG IN softkey on the IP
Phone UI screen. Valid values are
0
(disabled) or
1
(enabled). Default is
0
(disabled).
If the “
http digest force login
” parameter is set to
1
(enabled), after the phone boots, the LOG IN
softkey displays on the phone’s LCD. If the user presses this softkey, a username/password screen
displays, allowing the user to enter the configured username and password that is sent to the
HTTP/HTTPS server for digest authentication by the server. By default, username is “
aastra
” and
password is “
aastra
”. You can enter the username and password in two ways:
•
Using the configuration files, you can change the default values for the following parameters:
—
http digest username -
specifies the username to use for HTTP/HTTPS digest
authentication.
—
http digest password
- specifies the password to use for HTTP/HTTPS digest
authentication.
•
By enabling the “
http digest force login
” parameter (setting to 1) - the phone displays the
LOG IN key so the user can enter the default username/password via the IP Phone UI.
Configuring Broadsoft CMS Support via the Configuration Files
Configure Broadsoft CMS support on the IP Phone using the following parameters in the
configuration files:
•
http digest force login
•
http digest username
•
http digest password
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“HTTP/HTTPS
Authentication Support for Broadsoft CMS”
on
page A-99.