Db permits email addresses with no Person
Bug #335509 reported by
Guilherme Salgado
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
William Grant |
Bug Description
In the beginning, all email addresses had to be associated with a person, but recently this has changed, so we *can* have email addresses that are not associated to a Person. This has not been a problem until now, because we don't have any way of creating email addresses not associated with a person.
However, with the new SSO server, personless accounts will be created, thus creating email addresses without an associated person. And we have plenty of code which is not ready to cope with that (e.g. all callsites of PersonSet.
Changed in launchpad-registry: | |
importance: | Undecided → High |
status: | New → Triaged |
visibility: | private → public |
Changed in launchpad-registry: | |
milestone: | none → series-future |
Changed in launchpad-foundations: | |
status: | Triaged → Invalid |
Changed in launchpad: | |
assignee: | nobody → William Grant (wgrant) |
status: | Triaged → Fix Released |
tags: | added: disclosure sharing |
To post a comment you must log in.
I do not understand why this is High priority. I do not think PersonSer should know about email addresses that belong to accounts. I expect user profiles to be created when the user registers with launchpad, or logs in for the first time using the SSO.