SharePoint Group Expansion (Aspire 2)

From wiki.searchtechnologies.com
Jump to: navigation, search

For Information on Aspire 3.1 Click Here


SharePoint Group Expansion (Aspire 2)
Factory Name  com.searchtechnologies.aspire:aspire-scheduler
subType  default
Inputs  A Job containing a group expansion request
Outputs  A Job containing a group expansion result


This component uses the UserGroup SOAP web service from SharePoint to fetch users and user group information. Multiple calls are made to the web service - one to get all the users from sharepoint and one for each discovered user to get it's groups from SharePoint. All users and groups information is cached.

Additionally, if LDAP Group Expansion was performed before this component, SharePoint Group Expansion will attempt to fetch group information for any LDAP groups. LDAP (or Active Directory) groups are stored in SharePoint as regular users, so this component will invoke UserGroup web service for each one of them. This will resolve any nested groups between SharePoint and LDAP.

Configuration

Element Type Default Description
user string Username used to authenticate against SharePoint.
password string N/A Password used to authenticate against SharePoint.
domain string Domain used to authenticate against SharePoint.
siteCollectionsToScan/siteCollectionUrl string URLs of site collections from which groups will be gathered (more than one allowed).

Example Configurations

<component name="GroupExpansionScheduler" subType="default" factoryName="aspire-scheduler">
  <debug>${debug}</debug>
  <schedules>
  <schedule name="GECache" enabled="true">
  <cron>${geSchedule}</cron>
  <event>onGECache</event>
  <job>
    <![CDATA[
      <doc actionProperties="cacheGroups">
	<connectorSource>
	  <domain>${DefaultDomain}</domain>
  	  <username>${DefaultUserName}</username>
	  <password>${DefaultPassword}</password>
	  <groupPrefixSeparator>@</groupPrefixSeparator>
	  <siteCollectionsToScan>
            <siteCollectionUrl>${url}</siteCollectionUrl>
          </siteCollectionsToScan>
	</connectorSource>
	<displayName>SharePointConnector</displayName>
      </doc>
    ]]>
  </job>
  </schedule>
  </schedules>
  <branches>
    <branch event="onGECache" pipelineManager="Main" />
  </branches>
</component>