Customizing authentication html pages – Amer Networks E5Web GUI User Manual
Page 544

8.4. Customizing Authentication HTML Pages
User Authentication makes use of a set of HTML files to present information to the user during
the authentication process. The options available for HTTP authentication processing are as
follows:
•
When a user attempts to use a browser to open a web page they are directed to a login page
(the FormLogin page). After successful login, the user is taken to the originally requested
page.
•
After successful login, instead the user can be taken to a specified web page.
•
After successful login, the user is taken to a particular web page (the LoginSuccess page)
before being automatically redirected to the originally requested page.
HTTP Banner Files
The web page files, also referred to as HTTP banner files, are stored within cOS Core and already
exist by default at initial cOS Core startup. These files can be customized to suit a particular
installation's needs either by direct editing in Web Interface or InControl or by downloading and
re-uploading through an SCP client.
Banner files in cOS Core are of two types:
•
Banner files for authentication rules using Web Auth (HTTP and HTTPS login). These are
discussed below.
•
Banner files for the HTTP ALG. These are discussed in Section 6.3.4.4, “Customizing WCF HTML
Pages”.
Banner Files for Web Authentication
The web authentication files available for editing have the following names:
•
FormLogin
•
LoginSuccess
•
LoginFailure
•
LoginAlreadyDone
•
LoginChallenge
•
LoginChallengeTimeout
•
LoginSuccess
•
LoginSuccessBasicAuth
•
LogoutFailure
•
FileNotFound
Customizing Banner Files
The Web Interface provides a simple way to download and edit the files and then upload the
edited HTML back to cOS Core.
To perform customization it is necessary to first create a new Auth Banner Files object with a
new name. This new object automatically contains a copy of all the files in the Default Auth
Banner Files object. These new files can then be edited and uploaded back to cOS Core. The
original Default object cannot be edited. The example given below goes through the
customization steps.
Chapter 8: User Authentication
544