LDAP over SSL not working in RTC 3.0.x
In our upgrade environment for RTC 3.0 (and 3.01 beta), we cannot seem to get the jts server to accept our ldap SSL configuration, ldaps://ldapservername:636, as a valid LDAP server.
We are using the same settings that exist in our current 2.0.0.2 env, which works fine.
LDAPS is configured and working correctly in WAS, but when we try to setup the jts server we get the following error:
Cannot connect to LDAP directory ldaps://ldapservername:636.
If we configure the jts server with non-ssl configuration and WAS with SSL, this works fine.
Has anyone else encountered this issue and found a solution?
NON-SSL LDAP connections are disallowed in our environment, please advise.
We are using the same settings that exist in our current 2.0.0.2 env, which works fine.
LDAPS is configured and working correctly in WAS, but when we try to setup the jts server we get the following error:
Cannot connect to LDAP directory ldaps://ldapservername:636.
If we configure the jts server with non-ssl configuration and WAS with SSL, this works fine.
Has anyone else encountered this issue and found a solution?
NON-SSL LDAP connections are disallowed in our environment, please advise.
One answer
Hi Thomas,
can you please file a defect for this here https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.newWorkItem to discuss it with development?
Thanks,
Ralph
can you please file a defect for this here https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.newWorkItem to discuss it with development?
Thanks,
Ralph
In our upgrade environment for RTC 3.0 (and 3.01 beta), we cannot seem to get the jts server to accept our ldap SSL configuration, ldaps://ldapservername:636, as a valid LDAP server.
We are using the same settings that exist in our current 2.0.0.2 env, which works fine.
LDAPS is configured and working correctly in WAS, but when we try to setup the jts server we get the following error:
Cannot connect to LDAP directory ldaps://ldapservername:636.
If we configure the jts server with non-ssl configuration and WAS with SSL, this works fine.
Has anyone else encountered this issue and found a solution?
NON-SSL LDAP connections are disallowed in our environment, please advise.