|Administering the Community|
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. By default, the application doesn't use a directory server. Instead, it stores all user data in a database and performs authentication with that data. When you integrate with LDAP, Jive will authenticate against your directory server. During setup, you specify which users and groups defined in the directory server you want the application to use.
The instructions for integration assume that you are or have access to the administrator of your directory server, and that you're familiar with the Jive Admin Console. If you don't have this expertise, you may want to contract with Jive 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 on (true), directory server traffic can be logged, and user passwords can be printed in plain text to the application's 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.