function questions
| Project: | Hotspot captive portal |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Hello,
I guess I'm a bit uncertain as to how this is supposed to function. Right now my coovaAP is redirecting to my drupal home page. Where the normal drupal log in block is shown. Now what I'm uncertain of, is are the users logging in via the drupal user login, and getting authenticated against my radius server there? Or is that mearly to log them into drupal, and then they are redirected to another page in drupal that allows them to authenticate for internet. If so, where is that page, or am I suppossed to create a "page" with code embedded for login?
anyway. as of now, my users are getting redirected to my drupal home, when they sign in via the drupal login, they get redirected to a "No such page".
I guess I'm a little uncertain as to how this is supposed to work.
I"m also a little uncertain as to my settings in coova. Following these instructions here:
http://coova.org/wiki/index.php/CoovaChilli/WithDrupal
are useful if you have access to the chilli/config file, but the coovaAP provides a GUI page to input various info's and will not allow one to leave things blank.
so hoping I could get a bit of guidance and a point in the right direction.......
I'd so much appreciate the help. I think I'm pretty close, but I need some clarification as to how it's supposed to operate, then I might have a better idea what i need to do. I think it's a great idea, and I'd love to give it a whirl, and see how it does!!!
I'm gonna attach a couple of jpgs, with my configs......FYI
| Attachment | Size |
|---|---|
| chilli3.jpg | 41.83 KB |
| drupal1.jpg | 49.22 KB |
#1
I'm interested to know how you plan on using the module... as there are a number of ways it could be used.
The module right now just provides a login box for the hotspot - either a pure HTML one or the Javascript controller based one. The module doesn't coordinate, however, with the RADIUS server. So, you can only login to the hotspot using usernames and passwords already in your RADIUS server. The module allows you to login all visitors with a single username and password, but it'll be better once the module can 'provision' users into the RADIUS system itself. This kind of functionality will be possible when used with CoovaRADIUS (a standalone RADIUS platform we are working on at coova.org).
With respect to your screenshots... Try to remove your UAM Homepage setting and your UAM Format URL has a typo (change it to ?q=hotspot instead of ?=hotspot).
#2
Thanks for the response.
So it's not necc, that the hotspot be integrated with the drupal login at this time. I do want to authenticate hotspot via my already existing RADIUS user list. If users have to login seperately via to utilize drupal that is ok. Eventually, it would be pretty cool though.
I guess, if the users were redirected the the main drupal page, and there was a link there that would guide them to the login page, that would be ideal, without the necc, of having to log into drupal first. then they would have the option of simply using internet, or not, and logging into drupal and using it. I would most likely have to add drupal to my walled garden I assume.
Right now, I'm also mainly running into issues, with leaving certain fields blank in the CoovaAP GUI, It doesnt allow empty fields. Specifically, someone said I should leave the UAM secret field blank for the javascript login, but coovaAP doesnt allow me to to do that. Basically now, i'm looking at ssh into the router, and modifying it manually, although I dont have the info necc, to the that yet. I had read the config file was at /etc/chilli/config there is a file there, but I dont think its the one i'm looking for.
Initially i was having a hard time trying to wrap my head around how it was supposed to funtion, but It's getting clearer. thanks, and any more input, I'd love to hear it.
thanks for the efforts, its a great idea.
#3
typos.. it's always typos....anyway, it works, so far.
the only thing that I havnt figured out, that I would like to do.
As of now, users are redirected towards the main drupal page. from there they have to log into drupal, and are redirected towards the login page. which means a double login. So what I have done is provide a hyperlink on the main page, that swings them over to the login page, and bypasses the drupal login. The tech hangup I have right now, is that the hyperlink redirects to "http://xxx.xxx.xxx.xxx/?q=hotspot" which brings up a "you are not at a hotspot" page, which i sorta expected. normally with chillispot I would have a intro splash page with http://xxx.xxx.xxx.xxx:3990/hotspotlogin.php and that would do the trick,
but that doesnt seem to work.....any thoughts on that?
PS. I'm using the redirect method, not javascript. as my radius is set for PAP right now, I may change this, but for now it works.