Christian Schneider writes:
> thank you very much for this detailed and elaborated answer.
You're welcome. I'm sorry I couldn't be more optimistic about
implementing the approach in Mailman.
At some point we in the Mailman project should probably consider
changing the authorization model. The
Dear Stephen,
thank you very much for this detailed and elaborated answer.
I am very happy to have this well-founded evaluation of my approach!
Your rating will give me a good stand in discussion with my team leader ;-)
to drop the constraint of only having SSO authorized moderators and admins...
Christian Schneider writes:
> did you manage to disable the local registration (with django
> accounts)? I am trying to get rid of these locally registered
> accounts as well.
The easist way to do this is to require SSO authentication to access
webapps (this can be done in the front-end webse
Hello,
did you manage to disable the local registration (with django accounts)?
I am trying to get rid of these locally registered accounts as well.
Background:
I only want authorized accounts (provided by our SSO) to be owners or
moderators with the ability to manage lists...
So, if I block all
via Mailman-users writes:
> Thank you for the reply. Ultimately, I ended up digging deeper
> into the allauth docs, per your suggestion, and I went a little bit
> further with the "SOCIALACCOUNT_ONLY" option. It turns out that
> the errors I were seeing were related to the sign up button
>
Thank you for the reply. Ultimately, I ended up digging deeper into the
allauth docs, per your suggestion, and I went a little bit further with the
"SOCIALACCOUNT_ONLY" option. It turns out that the errors I were seeing were
related to the sign up button referencing a view that didn't exist.
