Overview of directory server integration steps

To set up directory server integration, you need to gather information about your LDAP server configuration, identify the location of your key directory server and tree, map your users and groups so Jive can synchronize to them, and then test your implementation to ensure it is successful.

Directory server integration relies on preparation and testing to be successful. If you use this list of overview steps to plan your integration, and if you run a test implementation to ensure that you have correctly identified the users, groups, and fields you want to sync with your Jive instance, you can avoid some frustrating missteps associated with integrating these two complex products.

Gather information about your server configuration

To complete the integration setup, you need the following information.

  • The address of your directory server and how it will communicate with Jive. If you are using Jive to host your community, you can contact Support for assistance with setting up the connection between these servers. Make sure you account for server referrals, especially if you use Active Directory.
  • The Base DN associated with the users you want to sync with Jive. You may or may not want to include all the users in your organization, so make sure your Base DN is associated with the part of the tree that includes the users you are targeting. Keep in mind that if you plan to map groups as well as users, your Base DN needs to be at a tree level that contains both users and groups. You can also narrow down your users by specifying a User DN relative to the Base DN during setup.
  • The DN associated with an Administrator account that has read access to your directory server. This account does not need to be linked to a Jive user.
  • The field identifiers associated with any directory service fields you want to sync to Jive profile fields. For example, the Username field is typically associated with the sAMAccountName field for Active Directory. A good method for obtaining this information for your directory server setup is to export an LDIF file.
  • Any LDAP filter expressions that are required to limit the number of users returned when you sync Jive to your LDAP tree. Without the filters, synchronizing to your directory server returns every user associated with the Base DN you supplied, and your Jive community may be populated with users who don't need to be there.
  • The field identifiers for any groups you want to map to permissions groups in Jive. You don't need to map any groups if you are going to manage permissions entirely in the Jive community. You will also need to specify an attribute such as member or memberOf that can be used to associate users and groups.

Connect your LDAP server with Jive instance

  1. Start the directory server integration setup by going to the configuration page in the Admin Console:
    • Admin Console > People > Directory Server
    • Advanced Admin Console > People > Settings > Directory Server Settings
    Note: The individual fields on this page have helpful tooltips that you can access by hovering on the question mark next to the field.
  2. Enter your connection settings and test the connection by clicking Test Settings at the bottom of the tab. If you cannot connect, you may need to check your credentials. The account you are binding with must have read access to users and groups for the entire subtree rooted at the base DN.
  3. Click Save to save your connection settings and display the rest of the configuration settings in tabs.

Map LDAP fields to Jive profile fields

  1. In the User Mapping tab, map any Jive profile settings you want to populate from your directory server by supplying an LDAP string. Fields for which you provide a mapping are updated from the directory server whenever a synchronization takes place. For more information, see Mapping users from a directory server.
  2. Click Test Settings to validate your mappings against the directory server. If the attribute you specified cannot be found, you see an error message identifying the problem.
  3. Click Save to save the mapping settings.

Synchronize permission groups

In the Group Mapping tab, decide whether to use and synchronize the permissions groups you have set up in LDAP or use Jive to assign users to permissions groups. (Note that group permissions have nothing to do with social groups in Jive.) You can choose to maintain some Jive-created permission groups even if you use LDAP-managed groups: however, make sure they are distinctly named.


Recommendations for synchronizing permission groups:

  • When syncing LDAP groups to Jive, you should sync only the groups used by Jive. If you leave the Group Filter with the default setting, Jive will sync all groups a user is assigned to in LDAP.
  • Maintaining less than 500 Jive user groups simplifies administration and minimizes any performance impact from having too many groups.
  • After mapping groups from a directory server, you need a migration strategy to switch back to Jive for maintaining groups.

For more information, see Mapping groups from a directory server.

Set up account synchronization

Use the User Synchronization tab to determine when and how user information must be synchronized between LDAP and Jive. For more information, see Synchronizing LDAP users.

A LDAP group is synced into Jive only when a user from that LDAP group logs into your community. So you may not see all your LDAP groups synced into the community once you create the groups, but they will be synced over some time. To minimize the impact, the sync runs in small batches after the user logs into Jive.

For more information, see Synchronizing LDAP users.