After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 379523 - Add captive portal authentication support
Add captive portal authentication support
Status: RESOLVED NOTGNOME
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2006-11-26 17:55 UTC by Guillaume Desmottes
Modified: 2008-11-05 16:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Guillaume Desmottes 2006-11-26 17:55:50 UTC 
More and more networks uses captive portal and forces users to authenticate on a web page before allow them to use the network.
It would be great if NM could automatically perform the HTTP authentication using login/pass previously stored in gnome-keyring.

I'm not sure if it's really doable but maybe something like that could work:
- when we're connected, try to reach a well-know HTTP URL
- if it's the good web page, fine we're online
- if not, parse the web page, detect the password field (the pass) and the other input field (the login)
- Use login/pass stored in gnome-keyring or ask them to the user and send it using a HTTP request
Comment 1 Antoine Mairesse 2006-12-21 18:23:57 UTC 
I've made an applet doing this kind of stuff using NetworkManager's dbus interface. You can find it on http://antoine.mairesse.free.fr/autologin-applet/

Feel free to contact me if you need some help with it.

If this enhancement is accepted and no one propose I will try but I've not done C since at least 6 years so I will take sometimes... :-)
Comment 2 Dan Williams 2008-11-05 16:12:52 UTC 
The best solution is an external applet like Antoine has done; the applet could even pull from the DHCP information exposed over D-Bus for the captive portal identification stuff or probe the portal when connected.  The auth info could be tied to a connection; but at this time I don't think I want to suck this functionality directly into NM.