Canonical SSO provider

Contact address on private team isn't caught by registration process

Bug #396582 reported by Stuart Metcalfe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Triaged
Low
Unassigned

Bug Description

I tried to create a new user with an @lists.launchpad.net email address from a private team. This sent me a 'confirm registration' email but subsequently produced an oops when I tried to complete registration. I would expect the registration process to detect that the email address would cause registration to fail and notify me instead of sending a mail.

Guilherme Salgado (salgado)
affects: launchpad → launchpad-registry
Changed in launchpad-registry:
status: New → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

The SSO server used for login and identity management is not a part of Launchpad which allows teams to have email address. This is a bug, but the systems are not tightly coupled.

Changed in launchpad-registry:
importance: Undecided → Low
Curtis Hovey (sinzui)
tags: added: disclosure
Curtis Hovey (sinzui)
tags: added: oops
Revision history for this message
William Grant (wgrant) wrote :

This is an issue with the SSO database: its EmailAddress table still contains all the old Launchpad team email addresses, not linked to any Account. They should be purged.

affects: launchpad → canonical-identity-provider
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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