It’s 9am on Monday 25th June 2012 and the Linkey project is officially kicking off.
What is Linkey
The project will provide a detailed case study of the use of OAuth as an authorisation protocol here at the University of Lincoln. Working closely with the university Library, we will examine how the OAuth 2.0 specification can be integrated into a ‘single sign on’ environment alongside Microsoft’s Unified Access Gateway.
Our intention is to show how OAuth 2.0 can be used as part of an access and identity environment in higher education that improves the student experience by:
- A consistent and user centric sign-in experience.
- A richer exchange of user information between applications.
- Easier development and implementation of new products.
A recent review of the university’s library systems and services indicated that we had around 10 core applications which provide access to over 150 other resources, all of which have different methods of authenticating users – some used LDAP to authenticate users (and so users use their network username and password) and others had their own database of users (which require a different passwords – and in some cases usernames – and every single one of these flows have a different sign in experience; some are web based with various designs, others are desktop based with a mixture of custom sign-in windows and Microsoft sign-in screens. Over 80% of user queries sent to the Library’s support email address around about problems accessing resources.
Outside of the library there are over 100 other systems and services that have visibility in the business processes across the university which also authenticate in a number of different ways.
All of these different authentication flows lead to a very inconsistent user experience and consistently for the last few years this has been highlighted in numerous student surveys.
I (Alex Bilbie) will be undertaking the majority of the work on the project. This will include researching technological solutions, engaging with end users, developing the open source OAuth 2.0 PHP server and working on the final implementation.
The principal user on the project will be Dave Masterson, Head of Electronic Library Services, who has been charged with improving the usability of our Library’s online services.
Tim Simmonds, Online Services Team Manager, will assume management and oversight of the technical implementation of both OAuth and UAG.
The high level work plan is a below:
|Gather user requirements||X||X||X||X||X||X||X||X||X||X|
|Evaluate available technologies and options||X||X||X||X|
|Technical development and implementation||X||X||X||X||X||X||X|
|Write case study||X||X||X||X||X||X||X||X||X||X||X|
|Write/submit conference paper||X||X||X||X||X||X|
|OAuth workshop ￼||X|
You can follow the day to day activity on our Pivotal Tracker project page.
The anticipated outcomes of the project are:
- A case study of our implementation of OAuth 2.0 together with Microsoft’s UAG product. We will provide draft sections of the final case study in 12 monthly blog posts, allowing for early peer-review.
- Continued development of our open source OAuth 2.0 server (based on my server code), including an implementation of the SAML 2.0 Bearer Assertion Profiles for OAuth 2.0 specification and other relevant extensions to the main standard. We aim to produce a ‘drop in’ solution for OAuth 2.0, in a similar way that the SimpleSAMLphp project supports SAML implementations.
- A public workshop on the use of OAuth 2.0 in Further and Higher Education.
- A conference/journal paper, based on our case study.
- Expertise in the implementation of an institution-wide infrastructure for AIM.