A ways back I looked into supporting campus authentication in some apps I was brainstorming and found the information rather lacking for our campus. It was also only IIS supported at the time which made me feel a little less secure about the whole thing. They now have an apache module and are working on single sign-on but I’ve scrapped any plans.
However, I am rather impressed by what CASE is doing. You can start by looking at a wiki page they have describing their system and yes, the wiki even supports the CASE logins. You can also see that they have perl, ruby on rails, drupal, zope and other modules available. With choices like that I would not be surprised if their adoption rate is rather high.
What led me to the wiki was that they now offer OpenID’s for anyone with a CASE login using the single-signon system. And from the posting:
It’s great to see people in academia playing around with identity and authentication like this. However, a commenter did point out the first thing that popped into my head:
Here at MSU faculty usually keep their NetID and students have it for around two years after graduation. It will be interesting how universities and colleges handle this type of policy as people start linking their identity with the university itself. It’s also a place that needs work for OpenID consumers. I’ve now lost the quote but someone made the comment that one of the crucial things missing is that consumers don’t allow multiple ID’s to be associated with an account, which would help prevent problems if one provider disappears, etc.
Something to think about. And to academia, here is a nice example of central services and information that can be useful. Transparency and documentation is a wonderful thing.