As of TeamConnect 5.2, clients will be able to integrate their instance of TeamConnect with SharePoint Online when it has been purchased as a part of an Office 365 subscription plan. SharePoint Online applications purchased through standalone subscriptions are currently unsupported by the out-of-the-box integration, as they do not supply access to Azure Active Directory, the authorization server that SharePoint Online trusts.

Prerequisites

The following list includes the software and files needed to follow this walk-through and authorize communication between TeamConnect and SharePoint Online:

•An Office 365 subscription plan that includes:

oSharePoint Online

oAzure Active Directory

o(Examples of such plans include: Office 365 Business Essentials, Office 365 Business, and Office 365 Business Premium)
 

•JDK 8
 

•The latest version of the following files:

oSharePointOnlineIntegration.class

oSharePointOnlineIntegration.properties
 

•The Baltimore CyberTrust Root certificate installed in your application server's trust store
 

•A PEM encoded X.509 public certificate

oThis certificate must be a PEM (Base-64) encoded X.509 public certificate, which will typically have either the .CER, .CRT, or .PEM file extension; if you are in a development environment or did not acquire such a certificate through your certificate authority of choice, you may create a self-signed one using the key length of your choice (4096 bits is recommended)
 

•A PEM encoded PKCS #8 private key complementary to the X.509 public certificate

oThis private key must be a PEM (Base-64) encoded PKCS #8 private key, which will typically have the .PK8 file extension; if you are in a development environment or did not acquire such a file through your certificate authority of choice, you may create one

oNote: Due to the sensitive value it contains, if this file has been supplied for the sole purpose of authorizing TeamConnect to communicate with SharePoint Online, it is strongly recommended after setting up your integration(s) that you move this file to a secure location or remove it from your system entirely; once this value is given to TeamConnect through the DMS Connector page, it will be obfuscated in the user interface upon entry and encrypted within the database for secure storage

(Optional) Creating a self-signed X.509 public certificate and PKCS #8 file on Windows 7

As this scheme requires the uses of public certificates, the following software may be used to create a self-signed certificate and private key file using the Microsoft Windows 7 SDK:

•Latest version of Microsoft .NET Framework 4

•Microsoft Windows SDK for Windows 7 and .NET Framework 4

•Latest version of OpenSSL for Windows

More information on setting up self-signed public certificates can be found in the Self-Signed Public Certificates for DMS section.