You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: