Alex Bilbie and Zackary Blank come on the show to talk about OAuth 2, which has been getting a lot of flamey bad press over the last year or two after the original author quit the project.
Why these guys? Well, Alex until recently was working at the University of Lincoln where they did a whole bunch of OAuth 2 work as auth for various API projects at the university. During this time he created the fully spec compliant CodeIgniter OAuth 2.0 Server, which was later replaced with a new generic PHP version for “The League of Extraordinary Packages”. It’s safe to say that Alex knows his shit when it comes to OAuth.
OAuth Case Study: A review into the uses of OAuth in higher education
The Linkey project has two main deliverables:
- Open source PHP libraries for OAuth2.0 clients and servers. Our code has been available for some time and is discussed in a previous post.
- A case study, which discusses the protocol and its uses.
Here is our case study.
Download the Case Study (PDF)
Read the Case Study online (Google Doc)
We welcome comments on the Case Study and invite you to leave them here on this blog post. Alternatively, you can contact us directly.
OAuth 2.0 PHP Library
Throughout the Linkey project I’ve been working on a number of PHP libraries that aim to make working with OAuth 2.0 easier.
The library is now at version 2.1, implements the entire core OAuth 2.0 specification and bearer token specification and has had over 1800 installations at the time of writing.
I’m very happy to announce that the University of Lincoln has agreed to transfer ownership of the code to the “PHP League of Extraordinary Packages” which means that it’ll continue to receive updates and be maintained by a number of developers around the world (myself included).
The server repository is now hosted at https://github.com/php-loep/oauth2-server and the client library is now hosted at https://github.com/php-loep/oauth2-client.
I have updated the wikis on both repositories with thorough documentation about how to use each library, and on the server library wiki I’ve added a lot more implementation about how to implement the library for common use cases.
My intention with all the code that has been written as an output of this project was that it would be as easy to use as possible and I’ve had some great feedback from developers:
— “Thanks for making your OAuth 2.0 server library public! It is people like you that make my job slightly more tolerable :)”
— “I wanted to thank you for your awesome library @alexbilbie :)”
— “Thank you for the great posts and lib”
— “If you drink, I will buy you a virtual beer!! What you built is awesome”
And finally in reply to a question that a developer asked me about how to do something with the library:
— “I’m really not surprised it was that simple – you’ve really built this with the end developer in mind. Once again, thanks very much for the info and the repo.”
To conclude I’m really happy with the code, I’ve learnt an awful lot as it has been developed and refined and I’m pleased that it’s new home will ensure long term sustainability.
Project dissemination at the Internet Identity Workshop
Last week I was in San Francisco for the 16th Internet Identity Workshop to disseminate the Linkey project and engage with those in the online identity communities.
The event was sponsored by many big names including Microsoft, Ping Identity, Google, Janrain, Yubico, Cisco, OneID and NetIQ. In attendance were employees from all of the sponsor companies as well as delegates ranging from freelance developers to information compliance officers at big companies to authors of many Internet specifications and protocols such as OpenID, OAuth and SAML. About half of hundred or so delegates had travelled from outside North America including about ten of us from Europe. Surprisingly I was the only delegate representing an educational institution.
The conference itself was un-conference style – i.e. each morning delegates would volunteer sessions which were then slotted into the timetable. A full list of all of the sessions can be found here. The sessions people put forward tended to either be very technical or were higher level, almost philosophical discussions.
Here is a list of sessions I attended (session notes can be found here):
- T1G: Native Apps – SSO
- T2B: Strong 2-Factor For All – Google and FIDO Alliance
- T3C: The OAuth Complicit Flow
- T4G: Identity Federation: Failed Consumer Experiences and WHat We Can Do About It
- W1H: OAUTH Client Registration
- W3B: OAuth 2 Bootstrapping from device to browser (technical)
- W4B: Google’s Auth goals for the next 5 years
- Google are strongly committed to OAuth!!!!
- W5I: OAuth 2 Federation – RS trust external AS
- TH2E: Practical DATA PROTECTION – Avoidance? EU and US ?
- TH3A: RESPECT CONNECT “Facebook Connect for Personal Clouds” OR “Social Login that Doesn’t Suck”
- TH4F: Self-Hosted Personal Clouds (FreedomBox and Raspberry PI)
The two main overarching topics throughout the event were “privacy” and “data ownership”. There were also a number of sessions about security, with one session that I attended by Google about 2-factor authentication resulting in quite heated discussion (namely because the work Google and the FIDO Alliance is not public and there is a high fee for membership).
Another interesting session was called “The OAuth Complicit Flow” (notes here) which had the premise of “what if the an OAuth authorisation server asked you to agree to “allow this application to connect to your account and murder someone” and there was no deny button. The discussion dealt with the issue of some applications asking for too many permissions, users not reading through the approve screens (similar to how users just accept EULA agreements) and applications refusing to let users access them unless they agree to allowing the application share stuff on their Facebook wall, or see the user’s friend list. Potential solutions that came out of this discussion was “reactive” permission requests as opposed to “preemptive” permissions – similar to how some iOS apps don’t ask for permission to send push notifications unless you click a button in the settings for that app.
I got the opportunity to have a chat with Mike Jones from Microsoft who has been leading much of the work on the OAuth 2.0 and OpenID Connect specifications. He answered a few questions I had about edge cases in implementations and he was interested in the PHP libraries I’d developed as part of the project.
I didn’t have the opportunity to talk at length about Linkey but in all the sessions I attended I tried to take part and I had some really interesting discussions with people about some of work that we’re doing in HE around open data and open APIs (including work on OAuth) and I was able to talk about some of the issues we faced with implementing OAuth in enterprise environments (because of incompatibility and lack of understanding compared to SAML).
I feel that the conference was definitely worth attending and I would encourage JISC and other interested parties in the education sectors to try and attend the next Internet Identity Workshop as I left feeling that we’re dealing with some very similar problems that even the very large organisations present such as Oracle are dealing with.
OAuth 2.0 has won the 2013 European Identity Award
Mike Jones, author of the OAuth 2.0 bearer token specification and significant contributor to the OAuth 2.0 specification itself, has announced on his blog that OAuth 2.0 has won the 2013 European Identity Award for Best Innovation/New Standard.
This is great news for everyone involved in writing the specification and who are implementing OAuth 2.0 solutions.