redirect.html is used to redirect to the status page
•
if user is not logged in, rlogin.html is displayed; if rlogin.html is not found,
redirect.html is used to redirect to the login page
3.
request for "/login" page
•
if user has successfully logged in (or is already logged in), alogin.html is displayed; if
alogin.html is not found, redirect.html is used to redirect to the originally requested
page or the status page (in case, original destination page was not given)
•
if user is not logged in (username was not supplied, no error message appeared),
login.html is showed
•
if login procedure has failed (error message is supplied), flogin.html is displayed; if
flogin.html is not found, login.html is used
•
in case of fatal errors, error.html is showed
4.
request for "/status" page
•
if user is logged in, status.html is displayed
•
if user is not logged in, fstatus.html is displayed; if fstatus.html is not found,
redirect.html is used to redirect to the login page
5.
request for '/logout' page
•
if user is logged in, logout.html is displayed
•
if user is not logged in, flogout.html is displayed; if flogout.html is not found,
redirect.html is used to redirect to the login page
Note that if it is not possible to meet a request using the pages stored on the router's FTP server,
Error 404 is displayed
There are many possibilities to customize what the HotSpot authentication pages look like:
•
The pages are easily modifiable. They are stored on the router's FTP server in the directory you
choose for the respective HotSpot server profile.
•
By changing the variables, which client sends to the HotSpot servlet, it is possible to reduce
keyword count to one (username or password; for example, the client's MAC address may be
used as the other value) or even to zero (License Agreement; some predefined values general
for all users or client's MAC address may be used as username and password)
•
Registration may occur on a different server (for example, on a server that is able to charge
Credit Cards). Client's MAC address may be passed to it, so that this information need not be
written in manually. After the registration, the server may change RADIUS database enabling
client to log in for some amount of time.
To insert variable in some place in HTML file, the $(var_name) syntax is used, where the
"var_name" is the name of the variable (without quotes). This construction may be used in any
HotSpot HTML file accessed as '/', '/login', '/status' or '/logout', as well as any text or HTML file
stored on the HotSpot server. For example, to show a link to the login page, following construction
can be used:
Page 521 of 695
Copyright 1999-2007, MikroTik. All rights reserved. Mikrotik, RouterOS and RouterBOARD are trademarks of Mikrotikls SIA.
Other trademarks and registred trademarks mentioned herein are properties of their respective owners.