Hi Peer-Joachim, do you use exactly the same settings in your server profile and self service? This means:
* server URL (name, port, protocol) * TLS setting The certificate settings are global so there should be no difference. Try restarting Apache in case some optimizer cache is wrong. Best regards Roland On 23.11.2016 10:31, Dr.Peer-Joachim Koch wrote: > Hi, > > > we just exchanged our old openldap+samba3 setup and moved over to SAMBA4. > > After importing the server certificate into the config we can use LAM > PRO again. > > However the self service will not talk to the samba4 server, neither on > port 389 > > nor on 636. > > Where to I have to enter the certificate information for the self service ? > > The certificates are sub certificates signed from the Telekom (in the > last step), > > so if the Telekom CA is trusted, the certificate should be trusted, too... > > Looking at at wire shows the exchange of the certificate. But it's hard > for me to read > > it packages on port 636 for me ;) > > Any idea or help ? > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Lam-public mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/lam-public >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------
_______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
