Password recovery on account creation is confusing for non-Launchpad users

Bug #415977 reported by Aaron Bentley
42
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Invalid
High
Unassigned
Landscape Server
Invalid
High
Unassigned
Launchpad itself
Fix Released
High
Guilherme Salgado

Bug Description

When an SSO user tries to create a Launchpad account, they get this message:
 "The email address <email address hidden> is already registered in the Launchpad Login Service (used by the Ubuntu shop and other OpenID sites). Please use the same email and password to log into Launchpad."

If they have forgotten their password, they will naturally try the "Forgotten your password? " option, but this doesn't work for non-launchpad accounts. They'll get: "Your account details have not been found. Please check your subscription email address and try again."

Nothing tells them that they need to use login.launchpad.net to recover their password.

I think it would be ideal if they *didn't* have to go somewhere else to recover their password. I don't know the technical issues, but it doesn't *seem* insurmountable-- login.launchpad.net works for Launchpad accounts, so can't we just use login.launchpad.net (or its underlying code) for all password recovery?

If there is a legitimate need to provide two different password recovery services, then:
- We could detect when people were using Launchpad's password recovery to recover an SSO password and suggest they use login.launchpad.net
- When account creation is denied due to an existing address, we should say "If you have forgotten your password, use login.launchpad.net (not this page) to recover your password." or something similar.

Related branches

Revision history for this message
Curtis Hovey (sinzui) wrote :

I think the issue here is that the user is in an intermediate state. There is an account created by some import process, but but it is not claimed. When the user tries forget password, we should be able to identify this situation and provide a link to claim the account to activate the user's profile.

Changed in launchpad-registry:
status: New → Incomplete
Revision history for this message
Guilherme Salgado (salgado) wrote : Re: [Bug 415977] [NEW] Password recovery on account creation is confusing for non-Launchpad users

It's easy to make Launchpad's password recovery work for SSO-only
accounts, so we should just do that.

 status triaged

Changed in launchpad-registry:
status: Incomplete → Triaged
Revision history for this message
Guilherme Salgado (salgado) wrote : Re: [Bug 415977] Re: Password recovery on account creation is confusing for non-Launchpad users

Curtis, the account mentioned by Aaron was an SSO-only account, so this
is not about a Person entry created by some import process.

 subscribe

Curtis Hovey (sinzui)
Changed in launchpad-registry:
importance: Undecided → Low
affects: launchpad-registry → canonical-identity-provider
Revision history for this message
Aaron Bentley (abentley) wrote :

I don't think this is a low-priority bug. I had to deal with two questions about it in CHR yesterday.

Revision history for this message
Stuart Bishop (stub) wrote :

I've added a Launchpad task too since a quick solution seems to be to make the Launchpad password recovery more intelligent.

Changed in canonical-identity-provider:
importance: Low → High
Changed in launchpad-foundations:
status: New → Triaged
importance: Undecided → High
Changed in landscape:
importance: Undecided → High
Revision history for this message
Christian Reis (kiko) wrote :

Also replied to feedback@ user today about this issue.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

FTR, sbordet on #launchpad had the same problem today. What was strange is the fact that after I initiated the password reset workflow through login.launchpad.net, the user got OOPS-1384G2331 when trying to login

Curtis Hovey (sinzui)
tags: added: chr
Revision history for this message
Karl Fogel (kfogel) wrote :

Just a "me too": I got this several times during CHR (more than 5, less than 20, beyond that I can't remember clearly -- the fog of war and all that).

Changed in launchpad-foundations:
assignee: nobody → Guilherme Salgado (salgado)
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in launchpad-foundations:
status: In Progress → Fix Committed
Changed in launchpad-foundations:
status: Fix Committed → Fix Released
Revision history for this message
Stuart Metcalfe (stuartmetcalfe) wrote :

Marking as invalid for the c-i-p project. We don't believe this is an issue with the new codebase.

Changed in canonical-identity-provider:
status: Triaged → Invalid
Changed in landscape:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.