Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDAP default settings for verify #143

Closed
popindavibe opened this issue Dec 16, 2017 · 4 comments
Closed

LDAP default settings for verify #143

popindavibe opened this issue Dec 16, 2017 · 4 comments

Comments

@popindavibe
Copy link

Hi all,
I spent a quite some time changing my filters after upgrade to Sympa 6.2

In the end I figured out thanks to sympa logs that the issue came from the ca_verify option which was marked as required/ optional and which does not allow you to specify where your CA actually is.
So all my testing locally was fine because of my CA being set up in /etc/ldap/ldap.conf, and my authentication was also fine because you can specify your CA there as well, but it looks like for data source setup there is no way to set your own CA file for it. Which means my TLS connection has to be set for none related to ca_verify.

Is this a feature or can we hope that this will be implemented in future updates? Maybe there is already a way, in which case I would very much obliged if you can point me to it.

@ikedas
Copy link
Member

ikedas commented Dec 20, 2017

looks like a duplicate of the bug (hopefully) fixed by #116 (See ed42d53).

@popindavibe
Copy link
Author

I am not sure if this is the same issue. I was mostly underlying the fact that we can specify a CA file and enforce verification in auth.conf while this is not a possibility at all when configuring ldap list filters to be used for mailing lists.

@ikedas
Copy link
Member

ikedas commented Dec 25, 2017

@popindavibe, can you show the settings both of auth.conf and "ldap list filters"?

@ikedas ikedas added the wontfix label Aug 16, 2018
@ikedas
Copy link
Member

ikedas commented Aug 16, 2018

Stagnated issue. Closed for the present.

@ikedas ikedas closed this as completed Aug 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants