Hi Francesco,
thanks a lot for your reply. I could fix this issue at the moment by
accepting "null" passwords in the policy. Next question, sorry for that. I
trusted the LDAP SSL certificate of the server and our CA in Tomcat, which
works fine, how to trust the "trustcacerts" for the LDAP SSL connection?
Thanks
Henri
<SSLHostConfig>
<Certificate certificateKeyFile="conf/iam.key"
certificateFile="conf/iam.crt"
certificateChainFile="conf/trustcacerts"
type="RSA" />
</SSLHostConfig>
Btw. some words to OD, all physical devices here are Apple units, the
servers are running VMware 6.7/7.0, with MACOS server and Terminal server (a
Macpro 7,1 Rack mounted), a lot of Linuxes (Ubuntu, Debian, CentOS, RHEL)
and 3 Win2016 VMs (which host almost only very unimportant stuff, exception
is Veeam). So we had never the need for an AD and don't use it (and I don't
like/trust MS - even before CVE-2020-1472). So to add AD functionality, I
installed Univentions AD (which is an synced SAMBA4 AD with Openldap). So
the simplest way ist to support both is add Syncope to bring both world in
snyc. Then we can fix the remaining 10%, which are not OD compatible.
--
Sent from: http://syncope-user.1051894.n5.nabble.com/
