Hi
Would be cool to have Kerberos authentication support.
Could you provide a PR?
No, for me the existing code is not really straightforward. It mostly assumes that setting SASL authentication only provides LDAP as a mechanism. The conditionals around that and the various configuration points/settings makes it really tedious. I think the code needs some refactoring to allow any mechanism to be swiftly implemented.
I forked, Kerberos is provided as the realm in LDAP. In target launch script, hostname and domain name need be a match to achieve expected behavior.
@djoq can you provide a PR for this feature?
Since the tests are failing @johansmitsnl, maybe it鈥檚 best to leave this the way it was. There exists issues discussing how this is more of a preference than a bug. It fixed the bug for my case, but as others has mentioned, this does require that unique email prefixes be set and causes conflicts in multi-domain/ email prefix uniqueness. Out of curiousity, which critical tests are failing?
@djoq I did not mention that tests are failing. What do you mean?
This issue was closed due to one or more of the following reasons:
If you think this happened by accident, or feel like this issue was not actually resolved, please feel free to re-open it. If there is an issue you could resolve in the meantime, please open a PR based on the current master branch so we can review it.
Most helpful comment
I forked, Kerberos is provided as the realm in LDAP. In target launch script, hostname and domain name need be a match to achieve expected behavior.