The discussion revolves around disabling all emails in Discourse except for registration-related ones, due to legal concerns. clay seeks a solution for a client who wants to manage user accounts without email notifications. sam suggests creating a plugin to disable emails or building a custom frontend using the API. Falco recommends using SSO (Single Sign-On) with a separate Rails or Django app for user management, which sam endorses as the best approach. clay asks for publicly available SSO examples, and sam points to the official Discourse SSO documentation here.
I have a client that wants to use Discourse on a project but cannot have Discourse emails coming through their email system for legal reasons. The instance of Discourse is going to be very heavily moderated/administered by some people in charge of the project. It seems there are two possible solutions here:
Admins create the accounts for the users and send them the credentials
Users receive only registration and password change emails and nothing else.
Right now, it doesn’t seem like either of those situations is possible. Am I correct in that assumption? Is there another way to establish and manage this community?
Ok, awesome. Do you know if there’s any publicly available example of a SSO source for Discourse? A Rails or Django app that’s ready to go, so to speak? I’ve worked in both, but if there’s a “perfect working example” out there that I can clone and use, that would be super handy.
