New Shibboleth IdP Login page mockups

[Tom Scavo]

On Tue, Dec 25, 2012 at 11:37 PM, Ryan Larscheidt
<larscheidt at doit.wisc.edu> wrote:
>
> Also, we've seen that tailoring the login page to display SP-specific information causes users to think the IdP's login page is actually the SP's login page.  As you can imagine, this perpetuates confusion about federation and single sign-off, because users don't realize that the IdP even exists.

Okay, I may have overstated the case. I agree with you that too much
SP information can be confusing (as in the case of the SP description)
but a well-placed reference to the SP display name could be helpful, I
think. Yes the login page should be IdP branded but that doesn't mean
it has to overpower everything else. The focus should be on the login
form. The actual Unicon login page (not the mockup Mike posted) is a
nice example of that approach.

Contributing to this problem is the fact that many SPs are still using
centralized discovery services with a non-SP brand. If we could fix
this problem, there would be little need to display SP information on
the login page.

> I understand there are some reasons to show Service Provider information in the IdP, like for attribute consent (uApprove) or a logout page that shows the user every SP they SSO'd into this session (unimr-logout), but not the login page.

Okay, well, I don't want to start a war or anything :-) The Shibboleth
software should be promoting recommended practices, to be sure. If
folks feel strongly there should be no SP information on the login
page, then the Project should distribute examples of that, of course.
I'm not sure it's all that black or white but...

Tom