Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

AEM 6.4 SharePoint Connector

Level 1
Level 1

We need the feature pack for SharePoint connector. According to documentation it says that the connector only supports SharePoint 2010 and SharePoint 2013.
Wanted to know few things:

1. Is there a feature pack that would support connecting AEM 6.4 to SharePoint 2016.
2. Does the connector work on AEM publish instances? If yes, is it recommended for end user login?
3. As the connector creates a JCR workspace can it co-exist with our existing JCR workspace of AEM or do we need a separate AEM instance?
4. Will connector support SSO based authentication using SAML?


Thanks in advance.


0 Replies

Hello Karan,

SharePoint connector supports the following versions:
Microsoft SharePoint versions:
  • Microsoft Office SharePoint Server (MOSS) 2010
  • Microsoft Office SharePoint Server (MOSS) 2013



SharePoint - Authentication Types

  •      Windows (Basic Authentication)
  •      Forms-based Authentication (NTLM - Token Based)

By default the connector exposes a single JCR workspace. The SharePoint server which is exposed by this workspace is set through the 'Sharepoint Server URL' configuration parameter.


The connector can also be configured for multiple workspaces. In this case, each workspace is associated with the URL of the respective SharePoint server that is exposed through the workspace. To add a workspace, add a workspace definition to the Workspaces parameter. A workspace definition has the following format: <name> = <url> where <name> is the name of the JCR workspace and <url> is the URL of the SharePoint server for that workspace.
In AEM, perform one more step apart from above configuration steps. Whitelist the ' ' bundle.
To whitelist bundles in AEM, perform the following steps:
  1. Navigate to the OSGi Management Console: http://localhost:4502/system/console/configMgr.
  2. Search for " Apache Sling Login Admin Whitelist" service.
  3. Select Bypass the whitelist.
  4. Add ' ' in whitelist bundles default
  5. Click Save.