Configuring User Identity Mapping

Jive supports external identity mapping by enabling you to map user identities using LDAP, SSO, or environments managed from within Jive.

You only need to configure identity mapping if SharePoint users are from multiple domains or if SharePoint User IDs are different from Jive User IDs.

You can configure user identity mapping to support two or more SharePoint domains that communicate with Jive. The following steps provide instructions for user identity mapping according to how your environment retrieves user information, which can be LDAP, SSO, or internally managed.

Note: External identity mapping support for SharePoint Connector can only be enabled once the required identity attribute values are made available to Jive. For more on this, see Required Attribute Settings

LDAP

  1. Determine which mapping set is the best fit for the required identity attributes.
  2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property:
    1. Set the sharepoint.identity.fieldname.override.sp-external-id property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it.
    2. Check and verify external identity mapping configuration System > Settings > SharePoint Connector > Identity Mapping .
    3. Click Synchronization.
    4. Proceed to Configuring Identity Mapping for SharePoint Locations.
  3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required). The SPC custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallyManaged.* system properties. They must be all be set to false, which requires a restart.
  4. Navigate to Admin Console: People > Settings > Profile and Homepage > Custom Profile fields.
  5. Click Edit Mapping for applicable fields, depending on the mapping set, which can be simple or composite configuration.
  6. Enter the LDAP attribute name(s).
  7. Run Synchronize LDAP or login as Jive user. This imports the LDAP required attributes values into either the simple or composite set of profile fields. Jive for SharePoint now has the correct SharePoint identifier(s) in its external identity store.
  8. Configure SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations

SSO

  1. Determine which mapping set is the best fit for the required identity attributes.
  2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property:
    1. Set the sharepoint.identity.fieldname.override.sp-external-id property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it.
    2. Check and verify external identity mapping configuration System > Settings > SharePoint Connector > Identity Mapping .
    3. Click Synchronization.
    4. Proceed to Configuring Identity Mapping for SharePoint Locations.
  3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required). The SharePoint Connector custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallyManaged.* system properties. They must be all be set to false, which requires a restart.
  4. Create Mapping. Depending on the SSO plugin implementation, you need to set identity attributes into the user's profile field(s) programmatically or by declarative means. For example, configuration - Spring mapping.
  5. Run Synchronization. Log in as jive user or run bulk synchronize (if available). This will bring in the required attributes values into either the simple or composite set of profile fields. Jive for SharePoint now has the correct SharePoint identifier(s) in its external identity store.
  6. Configure SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations

Internally Managed

  1. Determine which mapping set is the best fit for the required identity attributes.
  2. If Jive already has a profile field with this information, then you can override it using the sharepoint.identity.fieldname.override.sp-external-id property:
    1. Set the sharepoint.identity.fieldname.override.sp-external-id property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it.
    2. Check and verify external identity mapping configuration System > Settings > SharePoint Connector > Identity Mapping .
    3. Click Synchronization.
    4. Proceed to Configuring Identity Mapping for SharePoint Locations.
  3. Set sharepoint.identity.simple.fields.enabled and/or sharepoint.identity.composite.fields.enabled to true (restart is required. The SPC custom profile fields by default will be externally managed so ACTION IS REQUIRED for sharepoint.identity.profilefield.externallyManaged.*system properties. They must be all be set to false, which requires a restart.
  4. Navigate to Admin Console: People > Settings > Edit/Add user.
  5. Add or edit the identity value directly into the stock profile fields for either the simple of composite set. Upon save, Jive for SharePoint propagates the values into SharePoint external identity store.
  6. Configure the SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations
Up to: Administering the Jive-Side Plugin

Powered by Jive Software
© 1999-2012 Jive Software. All rights reserved. Follow us on Twitter @jivedocs