SharePoint Connector 1.2 Release Notes (v 1.9)

7 June 2010 

Atlassian released the Confluence SharePoint Connector 1.2.

The two big features of this release are SharePoint 2010 support and the much improved support for Integrated Windows Authentication (IWA). With version 1.2 of the Confluence SharePoint Connector, you can now connect Confluence to Microsoft SharePoint 2010 as well as SharePoint 2007. In addition, the connector offers full support for all the IWA protocols, now including NTLMv2 and Kerberos.

There are a number of other improvements too. You can now deploy the connector to additional SharePoint site collections at any time. The connector supports multiple AD domains, since it can now distinguish between two identical usernames in different domains. To see the full picture, take a look at the list of improvements below.

The SharePoint Connector now supports SharePoint 2010 as well as SharePoint 2007. The connector offers the same features for both versions of SharePoint:

• Embed Confluence pages and page trees into a SharePoint page, using the Confluence web parts. Click through from SharePoint to Confluence.
• Embed SharePoint lists and documents into a Confluence page, using Confluence's sp-list and sp-link macros. Click through from Confluence to SharePoint. Edit Office documents directly from Confluence and save them back to SharePoint.
• Enjoy automatic login (single sign-on) between Confluence and SharePoint.
• Search Confluence and SharePoint content together, retrieving a unified set of results.

The SharePoint Connector offers a number of options for configuring authentication between Confluence and SharePoint. Version 1.2 of the connector adds support for NTLMv2 and Kerberos. This means that the connector supports all of the Integrated Windows Authentication protocols. We have created handy guides and decision charts to help you choose the configuration that suits your environment, and detailed documentation about setting up each configuration.

Connecting from SharePoint to Confluence:

• The connector supports all of the IWA protocols (LM, LMv2, NTLM, NTLMv2, Kerberos).
• You can use IIS or Jespa.

Connecting from Confluence to SharePoint:

• Confluence on Windows can connect to SharePoint using all of the IWA protocols (LM, Mv2, NTLM, NTLMv2, Kerberos), using our new .NET NTLM proxy.
• When Confluence is not running on Windows, it can connect to SharePoint using LM or NTLM.

See our cool new guides to planning your environment with  SharePoint 2007 and SharePoint 2010.

At any time after the initial installation, you can now deploy the SharePoint Connector to more site collections. Just run the SharePoint Connector installer (Setup_WebParts.exe) and select 'Deploy to new Site Collection'. See our  documentation.

You can configure Confluence to connect to a number of Active Directory domains. With the latest release of the SharePoint Connector, you can configure the connector to pass the domain as well as the username when checking the user's permissions in Confluence. This means that the connector can distinguish between two users who have the same username in different domains. See our documentation for SharePoint 2007 and  for SharePoint 2010.

You'll notice that things just work better with the latest version of the SharePoint Connector.

• We have fixed a problem in the Confluence Pages Tree View web part. Before this release, SharePoint would automatically check out the page when a user changed the selection in the space dropdown list. Under certain circumstances, this could cause an error. The web part now displays a 'Make Default' option when the user changes the selection in the space dropdown. If the user selects the option, SharePoint will check out the page if necessary. Otherwise, SharePoint will not attempt to check out the page.
• When sending authentication credentials to Confluence, the SharePoint Connector now correctly passes credentials entered in the format 'DOMAIN\Username'. Before this release, the connector sent such credentials with an empty domain and the username set to 'DOMAIN\Username', which caused the authentication to fail. This bug is now fixed.
• See the complete list of fixes below.

For more information visit the Atlassian Marketplace.