Users Guide

Table Of Contents
333| Captive Portal Authentication Dell Networking W-Series ArubaOS 6.5.x| User Guide
{
var nameEQ = name + "=";
var ca = document.cookie.split(';');
for(var i=0;i < ca.length;i++)
{
var c = ca[i];
while (c.charAt(0)==' ') c = c.substring(1,c.length);
if (c.indexOf(nameEQ) == 0) return c.substring
(nameEQ.length,c.length);
}
return null;
}
var cookieval = readCookie('url');
if (cookieval.length>0) document.write("<meta http-equiv=\"refresh\"
content=\"2;url=http://"+cookieval+"\""+">");
}
</script>
</head>
<body bgcolor=white text=000000>
<font face="Verdana, Arial, Helvetica, sans-serif" size=+1>
<b>User Authenticated </b>
<p>In 2 seconds you will be automatically redirected to your original web page</p>
<p> Press control-d to bookmark this page.</p>
<FORM ACTION="/auth/logout.html">
<INPUT type="submit" name="logout" value="Logout">
</FORM>
</font>
</body>
</html>
Customizing Authentication Reply-Message to Captive Portal Users
In ArubaOS 6.4.x and earlier versions, captive portal authentication displayed pre-defined strings such
Authentication Successful and Authentication Failed to users in the log-in page. So, RADIUS attribute
Reply-Message was sent by RADIUS servers and it was not forwarded by Authentication module to the
Captive Portal module.
ArubaOS 6.5 introduces the support for customizing authentication Reply-Message to captive portal users in
the log-in page for better user experience. The purpose behind the Reply-Message is to return appropriate
information to the captive portal system.
For example, ClearPass can send a RADIUS-reject for various reasons, such as, authentication failed, bandwidth
limit exceeded, max. session reached, max. devices used. In ArubaOS 6.4.x, the user returns Authentication
failed message for all the reasons. In ArubaOS 6.5, ClearPass can now include the reason why it is rejecting in
the Reply-Message. So, ClearPass processes the Reply-Message on the web login form and informs the user
that The max. number of sessions has been reached is the reason for authentication failure.
So, another RADIUS attribute is added in the reply message to the Captive Portal module from
Authentication module with the following two restrictions:
l There can be multiple Reply-Message attributes in a packet but only the first attribute is considered.
l The length of the reply message is limited to 256 characters.
RADIUS server and Authentication servers are required to be configured accordingly to send the reply message
against authentication success or failure scenarios
This feature is implemented in the following ways:
l For internal captive portal case