When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists

[Florian Fuchs]

Currently user data held by Postorius is not neccessarily connected to Mailman. Once logged in, it should be checked if the user already exists in MM and a new user should be added to via the API if necessary.

[Ethan Fremen (mindlace)]

Hmmm... Doesn't this involve some level of disambiguation?

I.e. do we intend to deal with this case: user has mailman user from mail signup/ admin signup, but uses other auth method for web login, and so needs to associate their web auth with a mailman user?

[Florian Fuchs (flo-fuchs)]

Hi Ethan,

logging in to postorius using django.contrib.auth as well as using BrowserID requires an email address. We can use this address to look up previously created (mail/admin signup) user accounts using the mailman rest API. If none exists we should create one (creating new users is also an API feature).

Florian

[Florian Fuchs (flo-fuchs)]

Automatic (Mailman-)user creation should be optional (i.e. configurable in settings.py). If Postorius is part of a larger Django project where list management is only one aspect among others, it might be undesirable to add a new Mailman-user for every newly created Django user.