Connect Confluence Data Center to Rovo
Centralize your team’s knowledge across Data Center and Cloud sites by integrating your Confluence Data Center pages and blog posts into Rovo.
What is indexed?
The Confluence DC connector indexes these objects:
Pages
Blog posts
Comments
Attachments
For each object, it indexes these attributes:
Name
URL
Created date
Last updated date
Creator
Contributor
Document body
Space
Labels
Reactions
All parent pages
Number of page views
Before you begin
Rovo will always respect permissions. Users will only ever see content that they already have access to. More on connectors and permissions
The Confluence Data Center connector is supported in Confluence 9.4 and above, as well as in 9.2.6 LTS and later.
If you’ve enabled rate limiting, you may need to adjust your request limits to ensure content is seamlessly indexed in Rovo.
Overview
To connect Confluence Data Center to Rovo, complete the following steps:
Create an application tunnel or configure an allowlist - This step only applies to Confluence instances hosted on private networks. If your Confluence instance is available over the public internet, skip this step.
Create an incoming application link.
Set up the connector in Atlassian Admin.
Choose which spaces to include.
Step 1: Set up an application tunnel
If your Confluence Data Center instance can be accessed over the public internet, you can skip this step and proceed to Step 2.
If your Confluence Data Center instance is on a private network, you need to set up an application tunnel from your Cloud organization to your Confluence Data Center instance. You can also use an existing tunnel by adjusting its configuration. More on tunnels
Alternatively, if you prefer not to use tunnels, you can allowlist incoming connections or IPs for Atlassian Cloud products and sites in your Data Center instance. More on IP addresses and domains for Atlassian Cloud products
Create a new tunnel
Configure the required connections and upstream ports.
Go to Atlassian Administration. Select your organization if you have more than one.
Select Data management > Data sources > Application tunnels.
Select Create tunnel.
Go through the wizard to provide the details of your self-managed instance and generate the security key associated with your tunnel.
Add the key to your Confluence Data Center instance.
To be redirected to your instance, select Copy and process.
To give the key to the admin of the instance, select Copy, then Close. The key can be added manually in Administration > Application tunnel, by selecting Add security key.
Paste your security key and follow the steps in the wizard.
Your tunnel is created. Wait until the status is Connected.
Use an existing tunnel
To use an existing tunnel, modify the HTTP connector:
In your installation directory, edit the
conf/server.xml
file.Update the connector to include the attribute:
secure="true"
.
More on required connections and upstream ports
Step 2: Create an incoming application link
Create an application link in the administration of your Confluence Data Center instance to use in the connection process. About creating application links
In Confluence Data Center, go to Administration > Application Links.
Select Create link.
Choose External application > Incoming.
Select Continue.
Enter a name for your application link
Insert
https://id.atlassian.com/outboundAuth/finish
as the redirect URL.For application permissions, select Manage Subscriptions.
Select Save.
In the application links table, under Actions, select More actions (•••) > View credentials.
Make note of the Client ID and Client secret - you’ll need them when setting up the connector in Atlassian Admin.
Step 3: Set up the connector in Atlassian Admin
Access the setup screen for the Confluence Data Center connector in Atlassian Admin:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Apps > AI settings > Rovo.
Under Sites, next to the site you want to connect, select Add connector.
Select Confluence Data Center and press Next.
Configure Confluence Data Center:
Enter a name for your Confluence Data Center connection.
Select your Data Center network type:
Private network if your network is behind a firewall and can’t be accessed over the public internet. Select the application tunnel you previously set up.
Public network if your Confluence Data Center instance can be accessed over the public internet or you’ve allowlisted incoming connections or IPs instead of using tunnels. Insert the server base URL (including context path if applicable) of your Confluence Data Center instance.
Enter the OAuth Client ID and Client secret.
Review the disclaimer.
Select Next.
Step 4: Choose data to include
You can choose which spaces you want to index. All spaces are selected by default. You can also choose whether new spaces created in the future are included or not.
Before you start, it’s important to note:
The connector will only start indexing the content of included spaces once you’ve saved your selection of data to include. Before then, the connector will only index the list of all spaces including space names, space keys and space icons.
Blocking individual pages is not supported.
Once you’ve set up your connector, you can manage the indexed content:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Settings > Rovo.
Under Sites, next to Confluence Data Center, select More actions () and select Manage content.
Removing content
If you’ve chosen to exclude an already indexed space, we’ll remove it immediately from search. For more information on how long we store that data, see our data, privacy and usage guidelines.
Next steps
After you’ve finished connecting Confluence Data Center, your team members will see Confluence Data Center show up as a filter option in Search. They will be asked to connect before they can see results. This is required so Rovo can make sure your teammates only see results they have access to.
Depending on the amount of content in your Confluence Data Center instance, it may take some time for everything to be indexed and appear in Rovo.
Was this helpful?