If you are using Discovery Center version 4.14 or greater, please review this linked article for the newer SharePoint Connector.
The permissions mentioned in the article below as well as for other Discovery Center connectors are defined in the Permissions and Access section of the Discovery Center User Guide.
Our implementation of the SharePoint connector requires the Browse Directories and Use Remote Interfaces rights be granted to the account being used to index or action content. This right is automatically included for Full Control and Contributor permission levels but not for the Read permission level. If you wish to use an account with minimal read-only access, you must create a copy of the Read permission level with the Browse Directories and Use Remote interfaces rights included.
Once you have chosen the correct permission level to use, you must ensure that those permissions are applied to ALL site collections, sites, and document libraries that appear within the SharePoint URL being accessed. For example, it is common for a SharePoint URL such as http://server/sites/sitecollection/site/library to be made up of the below sites and libraries, each of which each must be provided the necessary permissions for success:
- Default Site Collection: http://server/
- Target Site Collection: http://server/sites/sitecollection
- Target Site: http://server/sites/sitecollection/site
- Target Library: http://server/sites/sitecollection/site/library
Note that any content in the Default Site Collection will not be indexed unless explicitly requested. However, indexing the target locations will fail if necessary permissions are not applied to the default site collection.
SharePoint servers which do not have a default site present at root level (i.e. at http://server/) are not currently supported.
It is also important to be aware that discovery will not traverse different site collections even though the hierarchy within the SharePoint URL may suggest this would happen. In the example above, although the URLs overlap, the Target Site Collection is not a logical child of the Default Site Collection and so cannot be discovered by an index defined for the Default Site Collection. Any site collection must be addressed by its own index in Discovery Center and if relevant the guidance in the Discovery Center documentation on the handling of overlapping indexes must be adhered to.
Once your target account has permissions setup for SharePoint, supply the index with a set of Network Credentials in Discovery Center. Because of the way the SharePoint Web services are built, the account must be configured in an Email address format for Both O365 and On-premise deployments. On-premise credentials will need to be entered in UPN format, ie. TestAccount@TestDomain.com
If you encounter issues indexing content in SharePoint after all of the above is in place, refer to the article Diagnosing SharePoint Access Issues.