search for: tocc

...gt;>> https://gwarband.de/openldap/trace.dump >>> >>> The bugreportinglink from openldap: >>> http://www.openldap.org/its/index.cgi/Incoming?id=8615 >>> >>> I hope you can help me. >>> >>> Regards. >>> Tobias Warband -- toCc.cz

...>> >>>>> The bugreportinglink from openldap: >>>>> http://www.openldap.org/its/index.cgi/Incoming?id=8615 >>>>> >>>>> I hope you can help me. >>>>> >>>>> Regards. >>>>> Tobias Warband -- toCc.cz

...nk from openldap: >>>>>>> http://www.openldap.org/its/index.cgi/Incoming?id=8615 >>>>>>> >>>>>>> I hope you can help me. >>>>>>> >>>>>>> Regards. >>>>>>> Tobias Warband -- toCc.cz

...t;> http://www.openldap.org/its/index.cgi/Incoming?id=8615 >>>>>>>>> >>>>>>>>> I hope you can help me. >>>>>>>>> >>>>>>>>> Regards. >>>>>>>>> Tobias Warband -- toCc.cz

Hello, I have also installed LE certs. But nothing helps, I have double-checking all certs. ldapsearch with -ZZ works see: https://gwarband.de/openldap/ldapsearch.log I have also uploaded the TLSCACertificateFile, maybe I have a failure in the merge of the two fiels: https://gwarband.de/openldap/LetsEncrypt.crt And also I have uploaded my complete openldap configuration:

I've replicate the settings from ldapsearch to dovecot but no success. To the certificate: Yes it's a *.crt file but I have linked the *.pem file to it and dovecot has read access to that file. I have enabled the debugging in dovecot and have uploaded the output: https://gwarband.de/openldap/dovecot-connect.log And the other site with ldapsearch:

The serverlog of openldap with loglevel "any": https://gwarband.de/openldap/openldap-connect.log Note: openldap waits 1 Minute before he says "TLS negotiation failure" after the connect. and dovecot says direct "Connect error" I've also delete the TLSCipherSuite from openldap. Tobias Am 2017-03-18 14:01, schrieb Tomas Habarta: > Increase log level on server

I've tested your soulution, but it also says the same error. I've tested all combinations of: - tls_ca_cert_file = <cert> - tls = yes - tls_require_cert = demand Every time it says "Connection error". Only when tls is uncommented it says "TLS required". Additional information from my contact with the openldap-technical mailing list: The

Hi, been running Dovecot 2.2.27 against OpenLDAP 2.4.40 normally over the unix socket on the same machine, but tried over inet with STARTTLS and it's working ok... I would suggest double-checking key/certs setup on OpenLDAP side; for the test I have used LE certs, utilizing following cn=config attributes: olcTLSCertificateKeyFile contains private key olcTLSCertificateFile contains

That's something you probably want to do on the edge instead of message store, so a better place might be relocated_maps if you use Postfix. With that you can easily customize your ldap search base for accounts-to-be-deleted OU... T. On Mon, Jan 29, 2018 at 06:53:20PM +0100, lists wrote: > Hi, > > The question can perhaps be made more generic like this: > > Can dovecot

Hello, just want to report a slightly confusing log entry on auth-debug level I have encountered while setting up Kerberos auth. Users are stored in ldap, Kerberos makes use of the same ldap as its backend, goal was to enable users to use their principals in addition to simple login with mailAddress/userPassword combination. Sample entry relevant attrs: --- mailAddress: sn.gn at example.com

Hello, my IdP is kind of progressive and implemented RFC9068, where all access tokens now come with typ "at+JWT". Since the setup has used local validation, I had to switch and currently use introspection endpoint. Looked around at the src and there seems to be relatively simple check of the token typ checking the only fixed value of "JWT" -- do you think you could consider