Challenger's configuration interface is accessed through its own port
and protocol. The user will be prompted for a user name and password
before gaining access to it.
When you install the server with the install script you
get to choose which port and protocol the configuration interface
The settings for the configuration interface can be changed in
Global Variables/Configuration interface...
The configuration interface will usually run on a non-standard port.
If you need to access it from outside your local network you might
have to reconfigure your firewall to allow accesses to that port. If
you have forgotten the port you can find it in the debug log, usually
You can choose to use either the HTTP or HTTPS protocol for the
configuration interface. The default and recommended is HTTPS which
gives an encrypted connection. Using HTTP is a potential security
hazard, since the administrator's user name and password will be sent
in clear text. To be able to use HTTPS you must have the full version
of Challenger, with SSL and encryption.
When you install the configuration server with the HTTPS protocol, it
will use a test certificate. This is not secure, since the certificate
is the same in all Roxen Challenger distributions. You should replace
this with a self signed-certificate as soon as possible, and consider
getting a certificate from a certificate authority. The HTTPS page explains how to
User name and password
When you connect to the configuration server for the first time you
will be asked to set a user name and a password. This will become the
user name and password required to access the configuration interface.
They can be changed by the Security/Change password and/or