Feature #3377
openOAuth2 authentication in captive portal
0%
Description
In Captive Portal we have native, ldap and radius authentication. Today, a lot of authentication systems provide OAuth2 backend. As CP authenticate users trought web, it can be a OAuth2 client.
My idea is to add a new "OAuth2 Authentication" after "RADIUS Authentication" on CP configuration.
O RADIUS Authentication Radius Protocol O PAP O CHAP_MD5 O MSCHAPv1 O MSCHAPv2 O OAuth2 Authentication OAuth2 accepted providers [ ] Amazon [ ] BitLy [ ] Box [ ] Dailymotion [ ] Dropbox [ ] Facebook [ ] Foursquare [ ] GitHub [ ] Google [ ] Heroku [ ] Instagram [ ] LinkedIn [ ] Microsoft [ ] PayPal [ ] RunKeeper [ ] SoundCloud [ ] Vkontakte [ ] Yammer [ ] Reddit [ ] Local1 [ ] Local2
Local1, Local2, ... are local providers found in /usr/local/oauth2/local-providers/, for example.
Of course, there is other parameters (key/secret for each oauth2 provider). And we have to open HTTPS for all selected OAuth2 providers -- tat is not very hard with "allowed hostnames".
I think that https://github.com/Lusitanian/PHPoAuthLib could be a good OAuth2 implementation to use. Add local providers is easy with this module.
Do you think such a feature is a good idea ? If there is no rebuttal, I can write a first proposal for a patch...