After a user has supplied login information on the remote login page, the login application
must submit an authentication request containing the user's login name, password, and IP
address to the controller by establishing an SSL session to the following URL:
Assume that the controller is not behind a NATing device, and that its IP address is
192.168.4.2. The subject DN in its SSL certificates is www.noc-cn3.com.
Defines the IP address of the controller or you could use a
domain name if you have defined one using the hosts file on
the Web server. (By default, the secure Web server on the
controller operates on port 8090. This can be changed on the
Management > Management Tool page if required.)
The controller requires that the contents of the Host HTTP
header match the actual domain name/IP address and port
the controller is operating on:
This is usually the case unless the controller is behind a
device that provides network address translation (NAT). In
this situation, the login application must manually forge the
Host HTTP header. The easiest way to do this is to define
login-url with the %i and %p placeholders. This returns
the domain name of the controller and the port number of its
secure Web server. The login application can then construct
the appropriate Host HTTP header.
Username supplied by the user.
Password supplied by the user.
IP address of the user's computer.