Allied Telesis AT-WR4500 manual Href=$link-loginlogin/a

Models: AT-WR4500

1 264
Download 264 pages 44.79 Kb
Page 237
Image 237

AT-WR4500 Series - IEEE 802.11abgh Outdoor Wireless Routers

237

RouterOS v3 Configuration and User Guide

 

 

 

if user is logged in, rstatus.html is displayed; if rstatus.html is not found, 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

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 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

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 should 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 (.txt, .htm or .html) file stored on the HotSpot server (with the exception of traffic counters, which are available in status page only, and error, error-orig, chap-id, chap-challengeand popup variables, which are available in login page only). For example, to show a link to the login page, following construction can be used:

<a href="$(link-login)">login</a>

Variables

All of the Servlet HTML pages use variables to show user specific values. Variable names appear only in the HTML source of the servlet pages - they are automatically replaced with the respective values by the HotSpot Servlet. For each variable there is an example of its possible value included in brackets. All the described variables are valid in all servlet pages, but some of them just might be empty at the time they are accesses (for example, there is no uptime before a user has logged in).

Common server variables:

hostname - DNS name or IP address (if DNS name is not given) of the HotSpot Servlet ("hotspot.example.net")

identity - RouterOS identity name ("AT-WR4562") login-by- authentication method used by user

plain-passwd- a "yes/no" representation of whether HTTP-PAP login method is allowed ("no") server-address- HotSpot server address ("10.5.50.1:80")

ssl-login- a "yes/no" representation of whether HTTPS method was used to access that servlet page ("no")

Page 237
Image 237
Allied Telesis AT-WR4500 manual Href=$link-loginlogin/a