This is a excellent module! I was actually planning to write my own companion module for Coova's hotspot module to do freeRADIUS integration, until I found this one.

Question: does this module permit unified login, i.e. such that logging into the hotspot also logs the user into Drupal as well? Or is the hotspot module itself supposed to be handling unified login?

My testing so far seems to suggest that the hotspot module presents its own, standalone javascript or HTML login forms for hotspot authentication, and that Ubercoova overrides Drupal user forms to maintain user integration between Drupal and freeRADIUS. However, logging into the hotspot forms does not also log the user into Drupal, and logging into the Ubercoova-overriden Drupal login forms doesn't log the user into the hotspot.

Is this so far by design? (I'll admit to likely having things misconfigured.)

Comments

westbywest’s picture

westbywest commented
Issue summary: View changes

spelling

cafuego’s picture

cafuego commented

Well, it sort of does a unified login, but the opposite way of what you're talking about I think.

Users *need* to exist in radius, so they are able to get online. If a user logs in to Drupal with a username that exists in radius but not in Drupal, a new Drupal user is created and the password is set to the radius password for that user.

If the users exists in both Drupal and radius, Drupal will check the entered password against the radius password and *not* the Drupal password.

If a user exists in Drupal but not in radius, I think it'll check the Drupal password and let the user login.

The login forms do *not* log the user in to both the hotspot and Drupal. The Coova login form does convoluted javascript stuff and I was unwilling to hack that into the standard Drupal login form handler, not being particularly JS-proficient. Also, as JS goes I think it's pretty awful.

That said, a patch is more than welcome :-)

westbywest’s picture

westbywest commented

Thanks for the heads up about the sub-optimal nature of the hotspot controller JS.

On my implementation, I've simply decided it was best NOT to bind Drupal authentication with the hotspot auth, since the former requires a request back to the Drupal site, DB query, etc, while the latter can happen much quicker over RADIUS. I.e. logging the user simultaneously into Drupal and the hotspot would likely slow down the hotspot login process, as experienced by the user.

I have made various patches to the Ubercoova module, although not sure if those amount to patches useful to anyone else but me. I will submit any patches, as they arise, if they're non-trivial to anyone else.

westbywest’s picture

westbywest commented
Issue summary: View changes

spelling