3 ms·
These are all exactly the right questions and challenges we are encountering, and we have no good answers. In all cases, customer IT would prefer vendors did no
by imglorp 4y ago
These are all exactly the right questions and challenges we are encountering, and we have no good answers. In all cases, customer IT would prefer vendors did not give them more work and risk.
We could support LDAP instead of OAUTH, yes, but for the shops that want us to speak TLS and DNS, they still have some hassle.
- throw0101a 4y agoJust to be clear: I'm asking for LDAP to be one possible choice. If an installation wants to use LDAP BIND they can use that, or if the want to use SAML they could use that, or OATH. But not at the same time: you get to choose one. Django Authentication system for example has a User object that allows different backends to feed into it: * https://django-auth-ldap.readthedocs.io/ https://django-auth-ldap.readthedocs.io/ * https://django-oauth-toolkit.readthedocs.io/ https://django-oauth-toolkit.readthedocs.io/ * https://stackoverflow.com/questions/22668434/saml-with-django-authentication https://stackoverflow.com/questions/22668434/saml-with-djang...
- imglorp 4y agoThanks for clarifying!