Confluence connection
If you will be creating datasets that process data in Confluence, you must complete additional tasks to enable this processing. Review the Confluence requirements and complete the connection tasks.
Confluence requirements
Prior to processing data from Confluence, you must have the following in place.
-
Confluence Data Center 7.19.x or later fully installed and functioning.
-
Retrieve the desired Confluence space keys for the spaces from which you want to process data.
-
Determine and configure the desired authentication to Confluence.
Retrieve Confluence space keys
When configuring a Confluence source in OpenText Core Data Discovery & Risk Insights, you define the spaces' key. You must retrieve the key for all spaces from which you want to process data.
-
Log in to the desired Confluence space.
-
For each desired space in Confluence, click Space Tools > Overview.
-
On the Space Details sub-tab, make note of the Key exactly as it appears.
You will enter this key when you create the source.
Authentication
You can use a user account or personal access token for authentication to Confluence sites and spaces. When creating sources, you will choose the authentication type and then define the necessary credentials. When creating datasets, you can inherit the credentials from the source or define separate credentials. You must ensure that the credentials defined for each dataset have the necessary permission to access each space defined in the dataset.
IMPORTANT: If you choose to authenticate using a personal access token, you must still create the user account . You will create the token for this user account.
Create a Confluence user account
For OpenText Core Data Discovery & Risk Insights to process Confluence data, you must create a user account in Confluence with the View permission. You will enter the credentials for this account when you create Confluence sources and datasets.
The user account must be specifically created for authentication by OpenText Core Data Discovery & Risk Insights and may not be used by any other application or activity.
Consider the following sample scenarios using a Confluence user account for authentication. Additional scenarios are possible, based on your organization's needs.
-
You want to authenticate to Confluence and access all of your spaces using a single user account. You will create a single user account and assign it the View permission in every Confluence space to be managed. You will define this user account when creating Confluence sources and select to inherit credentials for each dataset created under each source.
-
You want to authenticate to Confluence and access your spaces using multiple user accounts. You will create multiple user accounts and assign each the View permission in one or more Confluence spaces to be managed. You will define one of the user accounts when creating a Confluence source. You can select to inherit credentials for datasets under the source or choose to override the credentials and define one of the other user accounts created for authentication. In this scenario, ensure that all spaces defined in the dataset are accessible to the defined user account.
-
Log in to Confluence Data Center and create a user account according to your standard procedures.
-
For each space you want to process data from, assign the View permission.
-
Make note of the username and password. You will enter this information when you create the source.
Create a Confluence personal access token (Optional)
You can use a personal access token to authenticate to Confluence. If you choose to do so, you must create the token for the Confluence user account just created. The personal access token inherits permissions from the user account.
The personal access token must be specifically created for authentication by OpenText Core Data Discovery & Risk Insights and may not be used by any other application or activity.
Using the same sample scenarios as discussed for creating the Confluence user account, but select to authenticate using a personal access token. In this case, you would define the personal access token associated with the created user account instead of defining the username and password for the user account. You will need to ensure that all spaces defined in the dataset are accessible to the user account associated with the defined personal access token.
-
Log in to the desired Confluence space as the new user created for connection.
-
Create a personal access token.
-
Make note of the token value. You will enter this information when you create the source.
Configure web proxy settings (optional)
The Confluence processor service controlled by the processing agent requires connectivity to the OpenText Core Data Discovery & Risk Insights cloud components, often located away from the local network where the agent host servers are located. Although direct connectivity is ideal, use of a web proxy may be required in some environments for the agent systems to reach the OpenText Core Data Discovery & Risk Insights cloud.
-
On the machine hosting the OpenText Core Data Discovery & Risk Insights processing agent, log on to the agent administration UI.
From the Start menu, click OpenText Core Data Discovery & Risk Insights Agent > Agent Admin.
-
In the navigation pane, click Advanced Settings.
-
In the Category list, click Confluence Processor.
-
Complete the following options.
Option Description Proxy address URL Type the URL of the web proxy.
Proxy bypass list Type a comma separated list of addresses that do not use the proxy server..
Proxy Bypass on Local Specify whether to bypass the proxy for local addresses.
-
Select True to bypass for local addresses.
-
Select False to not bypass for local addresses.
Proxy Password If the proxy requires authentication, type the password for the user account that will access the proxy server. Proxy Username If the proxy requires authentication, type the username for the user account that will access the proxy server. -
-
Click Save. You can close the agent administration UI.
Confluence deletion tracking
OpenText Core Data Discovery & Risk Insights tracks deletions of managed Confluence items by comparing what is present at the Confluence dataset path to what has already been processed. When a scan is performed against a Confluence dataset, documents that no longer exist in Confluence are removed from OpenText Core Data Discovery & Risk Insights.