Sp branding in idp discovery & login

636 views

Published on

Presentation given by Rod Widdowson at JISC Collections Publisher workshop on federated access on 14th July 2011

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
636
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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.
  • Sp branding in idp discovery & login

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

    ×