Configure a Microsoft SharePoint Online Content Connector

Microsoft SharePoint Online is a web-based document management and storage system. After you configure and enable a Microsoft SharePoint Online content connector, you can connect to it and pull content from Microsoft SharePoint Online into Oracle Content and Experience.

A Microsoft SharePoint Online content connector enables you to import assets from the Microsoft SharePoint Online repository into Oracle Content and Experience. As an Administrator or Developer, you can configure a Microsoft SharePoint Online Content Connector from the Integrations menu in an Oracle Content and Experience instance.

To configure a Microsoft SharePoint Online content connector:

  1. Get the Oracle Content and Experience host name and authorization URL details.
    1. Sign in to Oracle Content and Experience as an Administrator or Developer.
    2. Click Integrations in the Administration area of the navigation menu on the left.
    3. In the Integrations menu, choose Content Connectors.
    4. Click the check box next to the Microsoft SharePoint Online content connector.
    5. Click Edit, or you can click the link to get to the Edit page.
    6. On the General tab, note the Redirect URL, which will be in this format:
      https://<hostname>.<domainname>.com:<port>/documents/web/AR_COMPLETE_AUTHORIZATION

      The Redirect URL field is truncated. Double-click the field to copy the value to your clipboard. You'll need to provide this value later in the SharePoint URL field on the Custom Fields tab.

  2. Create a SharePoint Online app:
    1. Sign in to Microsoft Azure at https://portal.azure.com/:
      1. Pick an account that has your Microsoft user name.
      2. Enter your Microsoft password.
      3. Choose Office365.
      4. Click Sign in.
      5. Click Yes to stay signed in and reduce multiple sign-ins.
    2. On the Azure services page, click App registrations.
    3. On the App registrations page, click New registration.
    4. On the Register an application page, enter a name and choose the account types that can use the application. At the bottom, paste a redirect URL and then click Register.
    5. On your application's page, click Certificates & secrets in the left menu, and then click the New client secret button on the page.
    6. Under Add a client secret, enter a description for your client secret, select Never under Expires, and then click Add.
    7. Click the Copy to clipboard icon on the bottom right to record the secret. You'll need to enter it later in the Client Secret field on the Custom Fields page for the content connector. Also click Copy to clipboard to record other details.
    8. On the API permissions page, click Add a permission to add a SharePoint Online permission, such as User.Read, a Delegated permission for SharePoint Online to sign in as the user and access an API. Another permission you might want to add is off-line access, which enables the refresh token.

      In addition to User permissions, you can grant AllSites, Myfiles, Sites, and TermStore permissions.

  3. Add the SharePoint Online connector to a repository.
    1. In Oracle Content and Experience, select Integrations on the left navigation menu.
    2. On the Integrations page, choose Content Connectors from the drop-down menu.
    3. In the list of content connectors, click the name of the Sharepoint Online content connector.
  4. Configure the Microsoft SharePoint Online content connector in Oracle Content and Experience.
    Description of sharepoint-connector-general.png follows
    Description of the illustration sharepoint-connector-general.png
    1. On the General tab:
      • The Name, Description, Connector service URL, and Redirect URL fields are prepopulated.
      • In the Connector tags field, you can assign tags that will be applied to assets pulled from the content connector (for example, the content connector name). This lets you search for all items from that content connector in an asset repository.
      • Make sure Enabled for end users is selected.

        You can review the Terms of use and Privacy Policy below the Enable for end users button.

    2. Click the Custom Fields tab.
      Description of sharepoint-connector-custom-fields.png follows
      Description of the illustration sharepoint-connector-custom-fields.png

      Enter the values for the following fields, some of which you recorded earlier:

      • Client ID (the value of Application id that you noted down earlier)
      • Client Secret (the value of the generated password)
      • SharePoint URL
      • Tenant ID
      • Access Scope
    3. When you're done, click Save.
  5. Add the connector to a repository.
    1. Click Content in the Administration area of the navigation menu on the left.
    2. Open an existing repository or click Create to create a new one.
    3. If you're creating a new repository, specify the repository name, publishing channels, languages, and other options.
    4. Under Content Connectors, select one or more connectors to associate with the repository.

      This menu lists all the content connectors that have been configured and enabled in your Oracle Content and Experience instance.

      If any of the connectors you select have content types associated with them, the types appear under Content Types.

After a Microsoft SharePoint Online content connector is configured, enabled, and associated with a repository, it's available in the asset repository for Oracle Content and Experience users to download content, through the Add drop-down menu Import from Microsoft SharePoint option on the Assets page.

Note:

An authorized application for a Microsoft SharePoint Online content connector must provide a link to https://account.live.com/consent/Manage, or to another location specified for a SharePoint Online content connector, with a clear indication that end users can go to that Microsoft site to revoke permissions at any time. If end users must take additional steps to disable the authorized application's access to end-user information, then the application must clearly indicate to end users the additional steps required to disable access. These requirements do not apply where Microsoft provides the end-user web interface.