Hi, I've developed an monolithic django project over the last 5 years. My team and I now want to add a new component to the software. The new component will be mostly independent, but need to share authentication and authorization at the least. For the end-user both the existing and the new component shall appear as one software, where a shared navigation moves the user from one component to another without the end-user noticing. I was researching for a while and came across django-oauth-toolkit, django-simple-sso, django-mama-cas and python-saml. As I see it, - OAuth2 is the standard nowadays for authorization via API. But doesn't seem to be the right solution for SSO across multiple django projects (or apps. We haven't decided yet, if projects or apps) - CAS seems to lose traction in in the market and I do not want to bet on a dying horse, but it kinda seems like the right solution for my challenge. - SAML seems to lose traction as well and I'm not even sure if it's the right approach. Also i can only find a "python" package, not a "django" package. - simple-sso seems to to what I want, but I can't find any relation to open standards that are being further developed, which would give me the confidence, that is it secure
Do you have an opinion or do you know the preferred/common approach to have single-sign-on across multiple django projects/apps. Thanks in advance. Any help is appreciated armadarama -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/90fe9d94-3057-4d48-9b3b-b1d5fb89dd59%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
