This documentation relates to an earlier version of the SharePoint Connector.
View

Unknown macro: {spacejump}

or visit the current documentation home.

This page is part of the installation guide for the Confluence SharePoint Connector. It tells you how to configure access to Confluence using Integrated Windows Authentication via Jespa. These instructions apply to the connector for SharePoint 2007.

On this page:

Overview

In this configuration both SharePoint and client browsers are authenticated against Confluence using Windows authentication provided by Jespa, a third-party implementation written in Java.

Use this Configuration when...
  • Your users are logged in to a Windows domain and access Confluence using a web browser that supports automatic pass through of Windows credentials. (See the recommended browser settings.)
  • You want your users to experience a seamless single sign-on experience when accessing Confluence.
  • Your Confluence installation is not running on a Windows server and you do not want to provision a new Windows server to provide an IIS proxy for Confluence (see Integrated Windows Authentication via IIS).

If you have not already seen our guide to planning your environment, you can refer to it for information that will help you select the best configuration for your environment.

Caveats

Supported Platforms

Due to the complex nature of this configuration and its reliance on third-party products, Atlassian is only able to offer support if your configuration matches these specifications:

  • Confluence is installed as a stand-alone Tomcat application server.
  • Confluence is configured to use LDAP integration to Active Directory for user management.

Anonymous Access

Anonymous access is not supported

You will not be able to get anonymous access for Confluence working when using this configuration.

When configuring Confluence with Jespa (as described in our guide) you will not be able to set up a satisfactory anonymous access mechanism, due to the requirements of the custom authenticator and the Confluence Base URL.

Atlassian is currently reviewing the suitability of using the third-party NTLM Authenticator for Confluence instead.

Additional Dependencies

Please consider the following additional dependencies:

  1. The configuration requires a custom Seraph authenticator for Confluence. If you are already using a custom Seraph authenticator, you may not be able to use this configuration.
  2. The configuration requires a third-party library that implements the Windows authentication protocols. See the section on Jespa below for details of this dependency.

About Jespa

Jespa is a Java software library that provides advanced integration between Microsoft Active Directory and Java applications such as Confluence. For more information, visit the Jespa website.

Authentication Methods

Jespa supports the following Windows authentication methods:

  • LM
  • NTLMv1
  • NTLM2 Session Security
  • LMv2
  • NTLMv2

Cost

Jespa is a commercial software package that has a licensing cost associated with its use. Atlassian does not have a redistribution agreement with IOPlex, the suppliers of Jespa. If you wish to use Jespa, you must arrange a purchase agreement with IOPlex directly.

Purchasing information can be found on the IOPlex website.

Installation Instructions

Follow the instructions on configuring Confluence to use Jespa for NTLM authentication.

Next Step

To continue with the installation of the SharePoint Connector, please install and configure the SharePoint feature.

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.