This section presents the configuration options available in Jive once the SharePoint-side plugin has been installed. In order to begin using the new SharePoint-based Jive widgets, please configure at least one SharePoint Location (see Adding a SharePoint Location to Jive (page 69) ).
Adding a SharePoint Location
When you add a SharePoint Location, you make Jive aware of a SharePoint site and all of its sub-sites. Once you have installed the Jive-side and SharePoint-side plugins, then you can add and configure SharePoint Locations in Jive. For more on installing the plugins, see Installing the Jive-side Plugin (page 66) and Installing the SharePoint-side Plugin (page 37)
Note: The SharePoint Location also allows Jive to be aware of any site collections that share the same initial URL path. For example, if there is a SharePoint site collection at http://sharepoint, and other site collections at http://sharepoint/sites/projectA and http://sharepoint/sites/projectB, only one SharePoint Location needs to be defined pointing to http://sharepoint. However, to use this approach, there must be a site collection at the shared portion of the URL (http://sharepoint).
When you add or update a SharePoint Location, the plugin adds or updates a corresponding OpenSearch Engine item, which is used to implement the SharePoint Search functionality. Perform any changes to the SharePoint Location itself to automatically copy the change to the OpenSearch Engine item for you. Once you complete the following steps, a SharePoint Site administrator can socialize a site (page 55) to Jive, which produces SharePoint activity in Jive and makes the SharePoint widgets (page 14) available within Jive:
• Add a SharePoint location as described in this topic. • Configure installation (page 50) in SharePoint. • Enable socialization in corporate policies (page 52) .
Note: The URL for the SharePoint site being socialized must start with the SharePoint Location External URL discussed below.
In the UI: Admin Console: System > Settings > SharePoint Connector > SharePoint Locations 1. Click Add SharePoint Location. Alternatively, you can click the Edit button next to an existing
SharePoint Location to update it.
Note: You can add as many SharePoint locations as you like, but one external/internal URL cannot start with the entire contents of another. For example, you can have http://sharepoint/sites/ projectA and http://sharepoint/sites/projectB as two SharePoint Locations, but you cannot have http://sharepoint and http://sharepoint/sites/projectB as two SharePoint Locations. In the latter case the http://sharepoint/sites/projectB started with the entire contents of http://sharepoint. For this case you can just have one SharePoint Location (http://sharepoint) to handle all of the sites.
Using an IP address for SharePoint it is not optimal and may cause issues related to Alternate Access Mappings on the SharePoint server. This will show up in the SharePoint trace log and System event log and may prevent some features of the connector from working properly.
• SharePoint Location Name: Enter free form name to use as a reference for the specified SharePoint location.
• SharePoint User Identity Mapping: After deciding whether you need to change the default user identity mapping, select the corresponding identity mapping: SharePoint External ID (Simple Profile field settings) or SharePoint External Username and Domain (Composite Profile field settings). For more on this, see Configuring User Identity Mapping (page 71) and Configuring Identity Mapping for SharePoint Locations (page 73) .
• Enabled: Select to enable SharePoint.
• SharePoint Location External URL: Enter URL to a SharePoint site as accessed by users. This is used for links referencing SharePoint provided in the browser to Jive users. This URL must resolve to a page accessible by users. This will allow any SharePoint sites under the referenced site to be accessible by Jive.
• SharePoint Location Internal URL: Enter URL to a SharePoint site as accessed by Jive. In most cases, this will be identical to the external URL above. However, this allows server- to-server communications to occur through a different handler on the SharePoint server(s) (a different IIS web site through the use of extended web applications). This allows for more flexibility in how security is handled for end users vs. Jive web service requests.
• Service Account: Account used to access SharePoint services on behalf of Jive users. This account requires read access to the SharePoint Location External URL, and it requires read
access to any site socialized from SharePoint. The permission for read access can be set
manually, but because SharePoint security is set up at the site collection level, it can be overridden at any site.Therefore, you can ensure that the service account always has read
access by creating a User Policy for the associated SharePoint web application and giving the service account Full Read permissions on the web application.
• External Search URL: Enter URL to a SharePoint search results page. The easiest way to determine the correct value:
• Log on to your SharePoint site.
• Find the search box (typically at the top right corner of the page). • Type in a search term and press Enter.
• Cut and paste the URL from the Search Results page into this field.
• Manually remove everything from a question mark ("?") character to the end of this value.
• Append ?k={searchTerms} to the URL, to ensure that the search terms you are using
will be forwarded to SharePoint.
• Search Scope: Enables you to create a scope that narrows SharePoint searches to only Names, Sites, or List, if desired.
Note: An advanced option allows you to set multiple Search Scopes. To do this, go to Admin Console: System > Settings >OpenSearch Engines and select Add Engine from Form. Use the Admin Console help for more information about this form. In the Search URL field, you need to enter the search URL that includes the type and value of the scope. The following list provides examples for each type of search scope.
• Scope by Name: http://<jive-instance-url>/spi-search.jspa?
searchTerms={searchTerms}&count={count}&locationID=1118&scope=<name>� • Scope by Site (URL): http://<jive-instance-url>/spi-search.jspa?
searchTerms={searchTerms}&count={count}&locationID=1118&site=<siteURL>� • Scope by List (URL): http://<jive-instance-url>/spi-search.jspa?
searchTerms={searchTerms}&count={count}&locationID=1118&list=<listURL> • Query Test Term: Enter a test phrase that returns results from SharePoint when a search is
to a Jive place, the URL of the SharePoint site needs to match the external or internal URL for one of the SharePoint locations. The matching SharePoint Location's service account needs to have read access to the corresponding site(s). A single SharePoint Location may map to multiple site collections as discussed previously. If the service account does not have read access to a particular SharePoint site, socializing that SharePoint site to Jive will fail. • Content from SharePoint activity stream: Use this option to manage content that you
maintain in SharePoint, but view in Jive. You can select one of the three options.
• The first option excludes content that has not been generated by a registered Jive user. • The second option enables you to specify an override user to claim that content. • The third option enables you to associate all content that is maintained in SharePoint
with a specific Jive user that you type into the Override User field. For example, you can associate all SharePoint content with one user so you can see at a glance which content is maintained in SharePoint.
Note: When you need to specify an Override User, make sure to use a valid Jive user. • Content Copied from SharePoint: Use this option to manage content copied from
SharePoint that will be maintained in Jive. You can select one of the three options.
• The first option excludes content that has not been generated by a registered Jive user. • The second option enables you to specify an override user to claim that content. • The third option enables you to associate all content that is maintained in SharePoint
with a specific Jive user that you type into the Override User field. For example, you can associate all SharePoint content with one user so you can see at a glance which content is maintained in SharePoint.
Note: When you need to specify an Override User, make sure to use a valid Jive user. 3. Click Update and then click Test next to your new SharePoint location before using the new
SharePoint-centric widgets and socialization features.
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 (page 78) . 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 (page 78)
LDAP
1. Determine which mapping set (page 77) 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:
a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78) .
b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain.
c. Click Synchronization.
d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73) . 3. Set sharepoint.identity.simple.fields.enabled and/or
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 (page 77) .
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 (page 73)
SSO
1. Determine which mapping set (page 77) 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:
a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78) .
b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain.
c. Click Synchronization.
d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73) . 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 (page 73)
Internally Managed
1. Determine which mapping set (page 77) 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:
a. Set the sharepoint.identity.fieldname.override.sp-external-id (page ) property to the name of the new custom profile field. When you create this custom profile field, see the rules for creating it (page 78) .
b. Check and verify external identity mapping configuration System --> Settings --> SharePoint Connector --> Multiple Domain.
c. Click Synchronization.
d. Proceed to Configuring Identity Mapping for SharePoint Locations (page 73) . 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
6. Configure the SharePoint Location in Jive. For more info, see Configuring Identity Mapping for SharePoint Locations (page 73)
Configuring Identity Mapping for SharePoint Locations
This topic helps you configure your SharePoint Locations if you want to provide user identity mapping for multiple SharePoint domains.
The following steps should be performed after you configure user identity mapping, which enables external identity mapping support.
1. From the Admin Console, navigate to System --> Settings --> SharePoint Connector --> SharePoint Locations.
2. Click Edit next to the location you want to edit. If you are adding a location for the first time, see Add a SharePoint location (page 69) to help you complete this page.
3. Use the following criteria to select the appropriate SharePoint User Identity Mapping. For more on this, see Configuring User Identity Mapping (page 71) .
• When the the Jive username and the SharePoint external identity (SharePoint login) are the same and SharePoint users are all from a single domain (if using Windows authentication), select the following profile field setting.
• Default (Jive username)
• When the the Jive username and the SharePoint external identity are NOT the same or the SharePoint users are from more than one domain (if using Windows authentication), select one of the following profile field settings.
• Simple when the fully qualified SharePoint external identity can be set into a single Jive user custom profile field: SharePoint External ID or [override field name]. For examples, see Mapping Sets for Custom Profile Fields (page 77) and Settings for Custom Profile Fields (page 78) .
• Composite when the fully qualified SharePoint external identity cannot be set into a single Jive user custom profile field. The SharePoint external identity will span two Jive custom profile fields: SharePoint External Username and SharePoint Domain Name. For examples, see Mapping Sets for Custom Profile Fields (page 77) and Settings for Custom Profile Fields (page 78)
4. Click Update to save your changes.
5. Verify SharePoint identity and connectivity by navigating to System --> Settings --> SharePoint Connector --> Diagnostics and clicking Diagnose next to the appropriate SharePoint location. Check user by entering user's Jive username and clicking Check Account.
How to Extract Attribute Values
Complex attribute values are ones that are buried in attribute strings and need to be parsed in order to use them. This topic shows you how you can extract complex attribute values from SharePoint and map them to Jive. This profile field mapping allows Jive to become aware of values that are buried in attribute strings by pulling out the significant pieces and mapping them to their counterparts in Jive. The following advanced regex properties are available to extract the target values from a string. You need to define the regex properties so they grab the right target value.
Note: If you make a change to any of the following transformation scenarios, then you'll need to run SharePoint Identity Synchronization (page 78) .
The following Simple Extraction table shows default values for the simple extraction. These settings extract a value so it can be mapped to the SharePoint External ID or Simple override profile fields.
The following Composite Extraction table provides extraction of default values and maps them to the SharePoint Username and SharePoint Domain Name profile fields.
System Property Setting (Default) Definition
sharepoint.identity.composite.formatProvider.username.regex.pattern(.+) Match 1 or more of anything sharepoint.identity.composite.formatProvider.username.regex.group1 Group 1 is the value to be
extracted
sharepoint.identity.composite.formatProvider.domain.regex.pattern(.+) Match 1 or more of anything sharepoint.identity.composite.formatProvider.domain.regex.group1 Group 1 is the value to be
extracted sharepoint.identity.composite.formatProvider.domain.regex.extract.lookupMap (advanced) { "lookup": { "key1": "value1", "key2": "value2" }, "defaultValue": "default" } Provides a JSON representation of a lookup associative array and a default value. Property string must be a valid JSON string. The following string is the default value.
The lowercase value of the raw profile field or, in this case, the extracted value based on the regex, will be looked up against the lookup map property.
1. If a value is found in the lookup map then it will be used.
2. If no value is found in the lookup map and the "defaultValue" property is defined that value will be used.
3. Otherwise the raw profile field or the extracted value will be used.
Note: Lookup functionality is only available for the SharePoint Domain Name profile field. An ERROR log entry will result if Jive cannot interpret JSON as a lookup associative array and a default value.
Examples
Check out the following examples of different ways to parse out the NETBIOS Domain name from the dn (Distinguished Name) LDAP attribute and transform it using a lookup table. This effectively maps the
System Property Setting Definition sharepoint.identity.composite.formatProvider.domain.regex.pattern(?i)((?:\s*DC\s*=\s*([0-9.a-
z_-]+)\s*(,|$)){1})
parses out the 1st domain (first DC key=value pair) or the string "JIVELAND" case- insensitive. Domain Name can consist of the following chars: 0-9a-z_-.
sharepoint.identity.composite.formatProvider.domain.regex.group2 Group 2 is the value to be extracted
The examples in this section use the following setting for
sharepoint.identity.composite.formatProvider.domain.regex.extract.lookupMap, which defines the defaultValue property, but does not define "JAF".
{ "lookup": { "jiveland": "JIVESOFTWARE", "pdx": "PORTLAND" }, "defaultValue": "JIVERS" }
If the exact value for the NetBIOS domain name cannot be easily made available to Jive, but the NetBIOS domain name already exists in the LDAP attribute you can use *.formatProvider.regex.pattern and *.formatProvider.regex.group and define these properties to parse out the target value. In this example, the target value is "JIVELAND", which is the value of the 1st DC key value pair.
Note: Before resorting to transformation of something like distinguished name, check to see if the LDAP attribute msDS-PrincipalName is available for each user. If so, this has the NetBIOSDomain\username