[RADIATOR] hotspot login portal

[Heikki Vatiainen]

On 12/03/2012 12:08 PM, John Lodge wrote:

> Are there any examples of html forms used as portal login forms to
> authenticate against radiator in order to see how the parameters are
> stored and posted to radiator for auth?

I'd say the HTML form is always set to post the form values (username,
password, etc.) to the controller, not to RADIUS server directly.

The controller then queries RADIUS server with RADIUS protocol and the
return value from the RADIUS server determines what the controller
returns to the browser and what optional redirection, walled garden and
other options it sets for the authenticating web user.

The above happens for portal pages that are stored in the controller
(internal portal) or that are external. With extranl portal the
controller redirects to user to a web server that can serve more
advanced content than the controller could.

See e.g. the links below and especially the second link that describes
external portal use with Cisco.

Note: What I described works more or less equally for e.g., Aruba,
Cisco, Exterme and Ruckus. I used cisco docs as an example since they
are quick to paste as links.

http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_user_accts.html#wp1120909

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008076f974.shtml

Thanks,
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.