2. Who am I, Why am I here? Primarily a developer: Extensive Discovery experience. Deeply involved in all the examples you’ll see today.
3. Take aways from this talk There is a very easy way you can massively help usability. Please do it. Their is an easy way to make significant further improvments. Please investigate at least.
8. A Bad Login experience No continuity of story. Each page is constructed in isolation. Branding, where present, is to do with “me”. Irrelevant branding present. No forward or backward reference. Result: confusion.
9. What can we do? (1) Developers & Operators (that’s me!) Unclutter the discovery GUI. Allow for forwards and backwards references. Give a continuity of experience. Branding (where appropriate). Cobranding (everywhere).
10. What can we do? (2) SPs (that’s you) Make branding available: Pictures Names Words An example:
14. This looks good. Can I play? Yes and it is easy. NO software changes (for SPs) Just send a mail to service@ukfederation.org.uk asking to add your logos But you should read (http://www.ukfederation.org.uk/content/Documents/MDUIRecommendations) As well (http://tinyurl.com/6xgejes) But I’ll summarise:
15. Adding a logo The logo is on your website. It has to be https:// protected. There are size constraints: Width between 64px and 350px. Height between 64px and 170px. Format constraints. PNG or GIF. Logo background (if any) should be transparent.
16. Adding words & a name The Name should be meaningful and short: “Foobar Scientific Journals.” The Description should be a brief phrase “Online access to all publications of Foobar inc since 1892.”
17. Is that it? In a word yes. If you want, you can Add more logos Text in different languages Other interesting stuff ... But you don’t have to.
19. Why build your own discovery? Using a Centralised Discovery Service means: The wrong IdP list: Too many IdPs to select from. Not enough IdPs to select from. No control. Although the new co-branding helps. It isn’t your website. We have always recommended SPs deploy their own Discovery Service.
20. Building your own discovery: old style Although was recommended it was hideously hard: Install Java Install another web server (Tomcat) Configure the GUI in this strange JSP thing. And keep it working. The example website was, at best, impenetrable.
21. Why this sucked. Hard work. New and alien technology Metadata drift. The CDS was “good enough” Little return for significant effort. Diverse look and feel. And yet many brave souls got it working.
22. There must be a better way Requirements: Easy to use. Easy to plagiarize examples. No new server side technology. Less than an hour to get done. We believe that we’ve met them.
23. Embedded Discovery Service No new server (its all part of the SP software) So no metadata drift. No new technology, just HTML. It is a page you own And is yours to brand. Lots of other cool stuff. Another demo
27. What is involved? Add some static pages to your web servers. Add the new pages: Add some templated stuff. Make it look liker your other pages. Configure Trivial for the SP configuration. Nonexistent/trivial for the web page. You are done. It is a bug this was not easy.
28. Required Software Shibboleth: Latest release OASP: Next release (but speak to the vendor) Guanxi: Current release? (but speak to the vendor) Others: Put me in touch.
29. Take aways from this talk There is a very easy way you can massively help usability. Please do it. Its just one mail message after all. Their is an easy way to make significant further improvments. Please investigate. Rod Widdowson rdw@steadingsoftware.com
Primarily a developerDo not get to speak to SPs often so thanksNot a Sp type personRoles as both s Shibboleth developer and a Developer for the UK Federation.
Branding: “I don’t know what it is, but I know it when I see it”Cobranding: the phrase I use to mean adding the brand of the relying party (SP if this is an IdP & vice versa) to the web page.
