Does anyone know of any issues with FR, LDAP and ...
# fusion-reactor
j
Does anyone know of any issues with FR, LDAP and custom SSL certificates? Brief summary, we deploy an image without FR all is good, we deploy with FR then we get
Caused by: javax.naming.CommunicationException: simple bind failed: {redacted}:636 [Root exception is <http://javax.net|javax.net>.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target],
which suggests it's not using/seeing the certificate?
The cert is shown as installed in
$LUCEE_HOME/server/lucee-server/context/security/cacerts
and a dev container running FR says it's using that truststore
d
@Jedihomer Townend I'm familiar with this issue because my certs somehow need to be added to the jvm keystore. However, I'm not familiar of this issue in the FusionReactor context. I'm just curious and perhaps you know. Why does our GlobalSign wildcard certificate have to be added to the jvm certs? Should it recognize my certificate as a valid cert provided by a valid authority? Its been years like and no one has been able to answer this question.
j
In our case, even though everything was saying it was the lucee truststore that was being used, we needed to add
-<http://Djavax.net|Djavax.net>.ssl.trustStore=/opt/lucee/server/lucee-server/context/security/cacerts
to our Java properties. With that there the requests worked.