Phil Leahy, Service Relationship Manager covers our commitment to the publishing community as part of our Publisher Manifesto. David Orrell, System Architect, runs through phase one of our new service provider product.
2. OpenAthens Service Provider as a service
• Phil Leahy (OpenAthens Service Relationship Manager)
• David Orrell (OpenAthens System Architect)
• Andy Anderson (OpenAthens Training Manager and QA
Analyst)
3. 1. Authentication: Providing the best possible end-user
experience
2. Single Sign-On: Enabling simple SSO within publishing
platforms
3. Establishing standards: Driving common standards for
interoperability
4. Facilitating discussions: Providing forums for discussion
5. Embracing change: Understanding that change is constant
5. • Overview of OpenAthens
• As an identity provider and a service provider
• How can we improve OpenAthens for publishers?
• What we’re doing
6. OpenAthens
• Web-based Single Sign-On (SSO) and identity
management
• Connect to multiple federations/communities using Open
Standards (SAML)
7. OpenAthens advantages
• For organisations/users
• Single account, seamless access across sites
• For publishers
• Integrate once, connect to multiple communities
9. Attributes
• Where is the user from?
• Who is the user (pseudonym)?
• User’s role or entitlement
• Name/email etc.
Organisation
(Identity
Provider)
Service Provider
Attributes
via SAML
11. User authentication in OpenAthens
• 2 routes for organisations
• Managed
• Local directory integration
• Managed identity as a service
• Upload via Web or bulk load
• REST APIs
• Self-registration
15. Customer feedback
• Not familiar with concepts of federated identity
• Installation and configuration steps unclear
• Changes take too long to take effect
• or require contact with Service Desk
Phase 1
16. Customer feedback
• Locally installed software required
• prefer to use an API
• Integrating with multiple applications is complex
• duplication of configuration and registration
• End-user experience inconsistent and confusing
Phase 2
18. New Service Provider Dashboard
• Guided setup process
• Clearer sign-posting of steps
• Much improved documentation
• Near instantaneous updates
• Faster turn-around on testing
• Registering for OpenAthens Federation
• No longer necessary!
Morning slot
Introduction
Hi, my name is Phil Leahy and I’m the Service Relationship Manager for all the publishers using OpenAthens products and services. I’m joined by David Orrell, the OpenAthens System Architect and Andy Anderson who doubles as our Training Manager and QA Analyst.
For almost 20 years we’ve provided software to publishers who want to enable access to their content in a more secure and extensible way than other methods can offer, such as IP authentication whose death seems permanently in ‘premature announcement’ mode, or more recently peer-to-peer SAML connections which are expensive to deploy and maintain, and yet can each only serve one customer. In the first part of this session David is going to talk about the immediate roadmap for our service provider offer, and then Andy is going to demonstrate the OpenAthens Publisher Dashboard which is the first deliverable of this project.
Before I hand over to David, I’d like to set this project in the context of the OpenAthens Publisher Manifesto which is in your delegate packs. Hopefully you’ll take this back to your organisation to use as a discussion point with colleagues, and we can send a PDF copy to you if you’d find it more convenient to distribute.
The five commitments in the manifesto are displayed here but the second and third items are the ones which the OpenAthens Cloud Service Provider addresses directly. In our experience, the size of a publisher or their technical capabilities has never been a clue to whether that publisher will choose to use open source code or third-party software to deploy support for federated access management. Not everyone wants to be a Shibboleth or SAML expert, and we have some publishers who are using our software after trying the open source route.
But that doesn’t mean we take anything for granted - we want to offer the best way of enabling federated access management; to let you integrate our products and services, and then get out of your way so you can get on with supporting your core activities.
There will be opportunities to ask questions after each section, so I’ll now hand over to David to talk about OpenAthens Service Provider as a service.
Outro
The OpenAthens Publisher Dashboard is due for release later this month, and we’re optimistic we will be able to release it on Tuesday of next week. If you’re already using the OpenAthens SP dashboard then you won’t need to do anything as the new dashboard will sit on the same URL, and if you’re only using the OpenAthens Federation Manager, a redirect will be in place to log you into the new dashboard. Our Phase I beta finished in October but we still want to hear your feedback. As you have seen, the workflow is a little different and although we’d like to think it’s more intuitive as a result, please let us know your thoughts.
We ran two webinars earlier this year to let customers track progress of phase I and we’ll be doing the same in 2017 for Phase II, so if you want to make sure you’re kept aware of those as they’re announced, you can make that known to any member of the OpenAthens team today.
We’d also like your feedback on the catering, so if you’d like to make your way to the dining room, we’ll be circulating so you can collar us with questions on anything you’ve heard so far today, even if it’s only about the quality of the sandwiches.