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 514304 - Support web-based authentication
Support web-based authentication
Status: RESOLVED DUPLICATE of bug 609870
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
: 584405 592303 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-04 14:23 UTC by David Jaša
Modified: 2012-08-24 14:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Jaša 2008-02-04 14:23:36 UTC
Some of networks I use on regular basis use web-based authentication. This means that computer gets IP and DNS settings from DHCP server but can only connect on ports 80/443 to authentication website (and all DNS requests return this site's address). User enters credentials at this site and if it authorizes him/her, DNS return normal results and routing for user's MAC (or MAC + IP combination) is allowed.

It would be nice if I cound tell NM that current network uses this type of authentication and if it could embed some HTML object where I could enter credentials and NM would store them for me.
Comment 1 David Jaša 2008-02-04 14:36:00 UTC
It would be also nice to be able to assign VPN connection to such connection as most of wireless connections don't use any encryption.
Comment 2 Dan Williams 2009-10-16 02:24:16 UTC
*** Bug 592303 has been marked as a duplicate of this bug. ***
Comment 3 Dan Williams 2009-10-16 02:24:55 UTC
Likely this would be done by using WISPR, which is what most of the current clients use.
Comment 4 Dan Williams 2009-10-16 02:41:51 UTC
*** Bug 584405 has been marked as a duplicate of this bug. ***
Comment 5 Pavel Simerda 2012-08-24 14:23:29 UTC
Marking the older bug as duplicate as the newer one has at least some answers :).

*** This bug has been marked as a duplicate of bug 609870 ***