funfake initiates a discussion on integrating Discourse authentication with an existing Django user database for an ecommerce platform, questioning if splitting authentication is advisable. hawm suggests the official Discourse SSO documentation as a starting point. funfake acknowledges the suggestion, noting that Django-SSO integration should be feasible, and promises to update the thread upon finding a solution. emrysr contributes a specific resource for Django developers regarding Discourse integration. The conversation expands as shawnngtq and foobarbecue express similar challenges, specifically mentioning the use of django-allauth, dj-rest-auth, and Django REST Framework, and ask if a solution has been discovered. Finally, alex.ehlke inquires about the progress and mentions considering building a synchronization system as an alternative approach.
Hi ! I’m really interested in Discourse for my ecommerce platform.
It would provide a great helping section for my users.
I’ve seen that Discourse has it’s own Auth methods. I was wondering if I could modify these in order to enable logins/registers through my platform (only).
Do you think it’s a great idea to split auths for better user management ?
Thanks for your reply. This topic is interesting. I imagine that someone already thought about Django-SSO so it shouldn’t be that hard to link Discourse with it.
I’ll keep your informed if I found my way into this.