IBM Sterling B2B: Configuring SB2Bi to connect Microsoft Sharepoint

From Wiki
Revision as of 18:48, 8 July 2025 by Ebasso (talk | contribs) (Created page with " Draft!!! Draft!!! Draft!!! Draft!!! Draft!!! Draft!!! Draft!!! Draft!!! = SharePoint setup = 1) MS Sharepoint: Create a site, 2) MS Sharepoint: Setup Permissions on MS EntraID for Restapi = SharePoint Integration Setup with IBM B2Bi = == Importing Certificates == Downloaded the Intermediate and Root certificates from the following domains: * login.microsoft.com * MY_SHAREPOINT.sharepoint.com These certificates were then added to the '''CA stor...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Draft!!!
Draft!!! 
Draft!!!
Draft!!! 
Draft!!!
Draft!!! 
Draft!!!
Draft!!! 

SharePoint setup

1) MS Sharepoint: Create a site,

2) MS Sharepoint: Setup Permissions on MS EntraID for Restapi

SharePoint Integration Setup with IBM B2Bi

Importing Certificates

Downloaded the Intermediate and Root certificates from the following domains:

  • login.microsoft.com
  • MY_SHAREPOINT.sharepoint.com

These certificates were then added to the CA store.

Retrieve and Convert Certificates using OpenSSL

Use the command below to retrieve the certificate chain:

openssl s_client -connect login.microsoft.com:443 -showcerts </dev/null \
 | awk '/-----BEGIN CERTIFICATE-----/,/-----END CERTIFICATE-----/{print > ("cert" ++i ".pem")}'


This will generate files like `cert1.pem`, `cert2.pem`, etc., for each certificate in the chain.

Import Certificates into Java KeyStore (JKS)

To import each certificate into a Java KeyStore:

keytool -importcert -trustcacerts -keystore truststore.jks -storepass changeit -alias login_cert1 -file cert1.pem

Repeat the `keytool` command for each `cert*.pem` file, using different aliases (e.g., `login_cert2`, etc.).

Tip: You can create the JKS file beforehand with an empty keystore if needed: <syntaxhighlight lang="bash"> keytool -genkey -keystore truststore.jks -alias temp -storepass changeit \

 -keyalg RSA -keysize 2048 -validity 1 -dname "CN=temp" -keypass changeit

keytool -delete -alias temp -keystore truststore.jks -storepass changeit </syntaxhighlight>

2. Creating System Certificate

A system certificate was created in IBM B2Bi.

The public part of this certificate was shared with the SharePoint team, who added it to their trusted certificates.

3. SharePoint Application Setup

The SharePoint administrator created an application and provided the following:

  • Tenant ID
  • Application ID

These values are required to configure the SharePointClient Adapter.

4. SharePointClient Adapter Configuration

The adapter was configured with the following parameters:

  • SharePoint URL: `https://MY_SHAREPOINT.sharepoint.com`
  • Tenant ID: (As provided by your SharePoint administrator)
  • Application ID: (As provided by your SharePoint administrator)
  • System Certificate: (The one created in Step 2)
  • Site Name: `CCTV-UI-ACC`
  • Document Library: `CCTV_ReasonsList`
  • Proxy Server: `No`
  • CA Certificate: All certificates captured in Step 1 and imported into the truststore
  • Min Thread / Max Thread / Timeout / ReadTimeout: Configure according to system performance and usage needs

Please ensure all certificates and IDs are valid and tested to avoid connection or authentication issues.



Ver também