By default, Jive doesn't use a directory server and stores all user data in a database from where it uses it for authentication. If your enterprise already uses an LDAP directory server such as OpenLDAP or Active Directory to manage users, you can configure your Jive community to integrate with it. During the setup, you can choose users and groups stored in the directory server for providing them access to Jive.
The instructions for integration assume that you are or have administrator access to your directory server and that you are familiar with the Jive Admin Console. If you don't have the expertise, you may want to contact Professional Services or another outside resource with expert knowledge about administering a directory server.
The Jive application database never caches or stores user credentials. However, if the LDAP system property
ldap.ldapDebugEnabled is set to
true, the directory traffic can be logged, and user passwords can be exposed in plain text to the
sbs.out log file if connections to LDAP are unencrypted (non-SSL). It is your responsibility to ensure that your LDAP communication runs over an SSL connection.