PacketFence - BTS - PacketFence
View Issue Details
0001594PacketFencecaptive portalpublic2012-11-05 09:352015-02-18 10:59
brancaleone 
 
normalminorhave not tried
closedopen 
3.6.0 
 
0001594: Google OAuth need access to ssl.gstatic.com
I tried the new OAuth feature in version 3.6.0 but i had a problem.
When being redirected to accounts.google.com to validate the access to my account, some content in the auth page is served by ssl.gstatic.com. This include the javascript files, and without thems i was not able to authorize access to my account, i was always redirected to https://accounts.google.com/o/noscript. [^]

To solve this, i added the ip 173.194.66.120 to oauth2-ips.conf (google section).

I also added a new zone file named-gstatic.com and hacked a bit in lib/pf/services/named.pm to make it loaded.

With those changes i was able to get an access through the captiveportal using my google account.
No tags attached.
diff gstatic-named.pm.diff (1,557) 2012-11-05 09:35
https://www.packetfence.org/bugs/file_download.php?file_id=171&type=bug
? named-gstatic.com (611) 2012-11-05 09:36
https://www.packetfence.org/bugs/file_download.php?file_id=172&type=bug
? oauth2-ips.conf (429) 2012-11-05 09:36
https://www.packetfence.org/bugs/file_download.php?file_id=173&type=bug
Issue History
2012-11-05 09:35brancaleoneNew Issue
2012-11-05 09:35brancaleoneFile Added: gstatic-named.pm.diff
2012-11-05 09:36brancaleoneFile Added: named-gstatic.com
2012-11-05 09:36brancaleoneFile Added: oauth2-ips.conf
2015-02-18 10:59lmunroNote Added: 0003916
2015-02-18 10:59lmunroStatusnew => closed

Notes
(0003916)
lmunro   
2015-02-18 10:59   
Obsolete bug tracker entries.
PF 4 introduced changes that either make these irrelevant or impossible to reproduce.

New issues are moving to github issues.