Hi Tom,
quite late answer, but maybe it still helps:
I had the very same problem using Reviewboard 6.0.2 and used the workaround
as showed by you, also finding it working but ugly. If finally managed to
solve it by:
1. cp
/usr/local/share/ca-certificates/
2. /usr/sbin/update-ca-certificates
I'm glad you have a workaround, and verified the problem. We have a
long-standing roadmap item to allow for selection of a SSL cert. We'll try
to prioritize that for an upcoming release.
Christian
On Fri, Jun 23, 2023 at 2:37 AM 'Tom Schäfer' via Review Board Community <
Hi Christian,
the ports to the LDAP(s) server are open, no more restrictions and we are
forced to use the 636 ports from IT. We use a selfsigned certificate and on
other systems we had to import the ca certificate (for example in our
Jenkins server). So i figured out how i can do this in
Hi Tom,
What LDAP server software are you using?
While I’d expect a different error code here, to check, do you use
self-signed SSL certs (or an in-house CA)? Is the cert still valid (not
expired)?
Are there any ACLs on the LDAP server that restrict what IPs can connect to
it?
Christian
On
Hi there,
I have the same issue now and i´m wondering if there is any solution to
this.
installed Reviewboard 6.0 beta1and tried setup LDAP authentication with
LDAPS.
*OS* : Ubuntu 22.04.2
*ReviewBoard Version* : 6.0 beta1
LDAP Config:
LDAP Server: ldaps://ldaps.mycompany.com:636
*Use TLS
Hi,
The error from python-ldap isn't always useful. However, this usually means
that it either can't communicate over the configured port, or there's some
other issue preventing communication. This *could* be SSL-related, but that
should usually result in a different error.
>From the Review
Hi Community Members,
I have installed Reviewboard 4.0.4 version and trying setup LDAP
authentication but unable to progress.
*OS* : CentOS 8
*ReviewBoard Version* : 4.0.4
LDAP Config:
LDAP Server: ldaps://ldaps.mycompany.com:636
*Use TLS for authentication*: Checked
Review Board LDAP Bind
