Comments on: New Copac interface http://copac.ac.uk/development-blog/2009/08/new-copac-interface/ What's happening behind the scenes at Copac Fri, 27 Jan 2012 19:08:08 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Copac at Interlend 2010. at Copac Developments http://copac.ac.uk/development-blog/2009/08/new-copac-interface/comment-page-1/#comment-3315 Copac at Interlend 2010. at Copac Developments Thu, 12 Aug 2010 15:22:55 +0000 http://copac.ac.uk/development-blog/?p=278#comment-3315 [...] an overview of our login feature that provides users with extra functionality (See post on: Copac’s new interface) and talked about Copac’s re-engineering project. (See post on: It’s official – [...] [...] an overview of our login feature that provides users with extra functionality (See post on: Copac’s new interface) and talked about Copac’s re-engineering project. (See post on: It’s official – [...]

]]> By: Ashley http://copac.ac.uk/development-blog/2009/08/new-copac-interface/comment-page-1/#comment-807 Ashley Tue, 11 Aug 2009 08:53:10 +0000 http://copac.ac.uk/development-blog/?p=278#comment-807 Owen, whichever authentication mechanism we support, we have to support the UK Federation (or Shibboleth if you prefer) as it is the JISC preferred authentication mechanism. The UK Federation is available to most, if not all, the UK academic research community and many other publicly funded organisations. And if you aren't a member of such an organisation, then anyone can sign up with ProtectNetwork or TypeKey and get a login that way. ProtectNetwork gives you an OpenID as well. I think that supporting multiple different authentication mechanisms is going to be confusing for users (never mind those that have to support the services), so we'd really like to support just the one authentication mechanism. The ID providers I mention above does make the UK Federation (and hence a Copac login) available to all. Owen, whichever authentication mechanism we support, we have to support the UK Federation (or Shibboleth if you prefer) as it is the JISC preferred authentication mechanism. The UK Federation is available to most, if not all, the UK academic research community and many other publicly funded organisations. And if you aren’t a member of such an organisation, then anyone can sign up with ProtectNetwork or TypeKey and get a login that way. ProtectNetwork gives you an OpenID as well.

I think that supporting multiple different authentication mechanisms is going to be confusing for users (never mind those that have to support the services), so we’d really like to support just the one authentication mechanism. The ID providers I mention above does make the UK Federation (and hence a Copac login) available to all.

]]> By: Owen Stephens http://copac.ac.uk/development-blog/2009/08/new-copac-interface/comment-page-1/#comment-804 Owen Stephens Mon, 10 Aug 2009 15:56:44 +0000 http://copac.ac.uk/development-blog/?p=278#comment-804 I guess the obvious question about logins is why not support OpenID for login? I guess the obvious question about logins is why not support OpenID for login?

]]>