You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, same as in TDI, I would recommend using 636 only (or with variable). The import of the TLS cert should only happen when port 636 or ldap_tls_enable=true is set.
You see, the setup is only possible if both protocols are enabled, but the only unecrypted connection is used.
The text was updated successfully, but these errors were encountered:
Hi,
I tried to install a system with an already installed LDAP server (Domino, Active Directory) on 389 only and then 636 only.
The TDI installation uses a Jinja2 template for profiles_tdi.properties
connections-automation/roles/third_party/ibm/tdi-install/templates/profiles_tdi.properties.j2
Line 19 in 6284e97
Here it needs 3 steps:
connections-automation/roles/third_party/ibm/tdi-install/templates/profiles_tdi.properties.j2
Line 53 in 6284e97
LDAP without SSL is not possible in production environments.
Was ND deployment makes it weird.
The LDAP server is added without SSL and port 389 here:
connections-automation/roles/third_party/ibm/wasnd/was-dmgr-config-ldap/templates/was_config_ldap.py.j2
Line 4 in 6284e97
But here
connections-automation/roles/third_party/ibm/wasnd/was-dmgr-import-tls-cert/templates/was_import_tls_cert.py.j2
Line 2 in 6284e97
So, same as in TDI, I would recommend using 636 only (or with variable). The import of the TLS cert should only happen when port 636 or ldap_tls_enable=true is set.
You see, the setup is only possible if both protocols are enabled, but the only unecrypted connection is used.
The text was updated successfully, but these errors were encountered: