There are, as of 2023-03-08, around 20 active User objects that are not bound to a Person object.
In the long run, setting active=False on these is the right thing to do, but in the short run, we have users (like Paul Hoffman) where IMAP service used one of these User object's usernames as the account identity.
We're working with Alexey to make it so that we can map usernames correctly so that Paul could log into IMAP with his active datatracker User/Person.
Once that's solved, we should run User.objects.filter(is_active=True, person=None).update(is_active=False) and close any places that such User objects can get created. (There have been 3 created in 2023 already, so this is an ongoing rough edge).
There are, as of 2023-03-08, around 20 active User objects that are not bound to a Person object.
In the long run, setting
active=False
on these is the right thing to do, but in the short run, we have users (like Paul Hoffman) where IMAP service used one of these User object's usernames as the account identity.We're working with Alexey to make it so that we can map usernames correctly so that Paul could log into IMAP with his active datatracker User/Person.
Once that's solved, we should run
User.objects.filter(is_active=True, person=None).update(is_active=False)
and close any places that such User objects can get created. (There have been 3 created in 2023 already, so this is an ongoing rough edge).