Hi guys, I’m coming in to pick your brains on something
We are setting up SSO between our no-code platform and our to-be Discourse forum. All’s working great, so yay on that. We are now, however, thinking about whether we should also keep Discourse’s ‘basic’ login via email + password.
My thoughts:
If we keep the SSO only, just people who are already our users could become members of the community. There is a free version of our product so if someone wants to join the community and they don’t have an account with us, they could register for the free plan. I, however, think that this might be a put-off for some folks.
If we keep both options, it might end up in duplicate accounts if someone uses an A email address to create the community account and later on a B email address to register with us.
I would hope that the majority of users would use the same email address . For the few that do end up with duplicate accounts, they could always ask an administrator to ‘merge’ the accounts via the Discourse admin panel.
If you are referring to DiscourseConnect with “SSO” then you don’t have an option since enabling DiscourseConnect will disable all other login methods.
That’s what I’m thinking as well. There are, however, some voices that say that the OAuth2 login gives us valuable information about the users because we see what they do in our product, what their business is about etc. I’m basically collecting opinions at this point
. For the few that do end up with duplicate accounts, they could always ask an administrator to ‘merge’ the accounts via the Discourse admin panel.
