Need to display consumer's logo and name on Sign in
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical SSO provider |
Fix Released
|
Medium
|
Danny Tamez | ||
Bug Description
Essentially, the change is about providing better information to the
user so that the experience of logging in/creating an account when
coming from a different site is not as shocking as it is now.
Our suggestion was to include the consumer logo, and maybe some other
details, so that the user feels confident about him entering information
on our site (as he recognizes the brand of the consumer that sent him
over to us).
As sometimes the user felt he was "stuck" on our site, let's make it
explicit that he can "go back" to the consumer (instead of plainly
'cancelling').
Things we need to do:
using the provided image as inspiration
1. Instead of displaying 'Sign In to {consumer}', we just say 'Sign In'.
2. We remove the 'You are here because ...' line
3. When we know where the user came from (a known consumer), instead of
saying 'or cancel', we say 'or go back to {consumer}' else we say 'or
cancel'
4. The 'gray' left content (where the login form is) should be aligned
with the right hand top of the 'logo area'
5. The 'go back to Ubuntu One' link at the top should not be present
(this is the case right now, but just in case :)).
6. The right hand side should display the consumer logo (but somewhat
smaller than its displayed in the mockup)
If you have any other suggestions as how we can make the shared
experience friendlier for the user, let me know, they are always welcome!
Related branches
- Michael Hall (community): Approve
-
Diff: 26 lines (+2/-3)2 files modifiedidentityprovider/templates/ubuntu/registration/login.html (+1/-1)
identityprovider/tests/test_models_openidmodels.py (+1/-2)
| Danny Tamez (zematynnad) wrote | #1 |
| Changed in canonical-identity-provider: | |
| assignee: | nobody → Danny Tamez (zematynnad) |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| tags: | added: kb-task sp-1 |
| tags: |
added: kb-improvement removed: kb-task |
| Changed in canonical-identity-provider: | |
| status: | In Progress → Fix Committed |
| Changed in canonical-identity-provider: | |
| status: | Fix Committed → In Progress |
| Changed in canonical-identity-provider: | |
| status: | In Progress → Fix Committed |
| Changed in canonical-identity-provider: | |
| status: | Fix Committed → In Progress |
| Changed in canonical-identity-provider: | |
| status: | In Progress → Fix Committed |
| Julien Funk (jaboing) wrote | #2 |
| Changed in canonical-identity-provider: | |
| status: | Fix Committed → Fix Released |
<pindonga> jfunk, so, there are two parts to this bug
<jfunk> ok
<pindonga> one we can test right away, and one we can test only after the redeploy (because I need admin access, which requires the db to be setup again, because the db reset during the weekend undid what we had changed there)
<pindonga> the one you can check right away is that if you access staging.
<pindonga> when you log in
<pindonga> login.staging.
<pindonga> where if you login directly it should say 'Continue or cancel'
<pindonga> as it doesn't know where you come from
<pindonga> the other part of the change (ie displaying the consumer logo) we need to update the sso consumer logo via the admin ui
<pindonga> that's why we need to have the redeploy first