Confluence does not explicitly specify LDAP protocols for pooling

The `com.sun.jndi.ldap.connect.pool.protocol` system property is not set explicitly by Confluence. This system property determines what protocols will be supported by the LDAP connection pool and defaults to `plain`, which only allows plaintext connections to be pooled.

This may not necessarily cause issues in production installations of Confluence as the initialization of the UserCache is performed very early during Confluence's startup and this initialization also applies the connection pool parameters set in the UI (`com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl#initialiseConnectionPoolSystemProperties(com.atlassian.crowd.model.application.Application)`). However if an LDAP interaction resulting in creation of the JNDI connection pool were to occur before those settings were initialized, the pool would be created with the defaults (unless Confluence was started with non-standard system properties). This would cause a severe performance downgrade for instances which use LDAP with SSL.

Even if this part of Confluence's startup is guaranteed to be executed earlier than the first LDAP interaction which could create a connection pool, a refactoring could change that assumption, introducing a hard to find performance regression.

This is prevented in Crowd and Bitbucket Server/DC by specifying the connection pool system properties explicitly.