for Atlassian Confluence.

In order to configure Confluence, you need the ability to create a token.

You can configure this source through the integration wizard on the frontend or you can use a local configuration file as outlined below.

The Confluence integration supports:

For basic authentication, you need to use the email address attached to your Atlassian account as username and a Confluence cloud token as the password in the configuration YAML file. For cloud configuration, the endpoint should contain atlassian.net.

Spaces in Confluence are automatically enumerated unless the spaces key is set to specific spaces. To skip specific spaces, use ignoreSpaces. Additionally, the spacesScope value can be set to ALL or GLOBAL or PERSONAL to indicate what type of spaces need to be scanned. In the absence of the spacesScope key, the value will be set to ALL. Please keep in mind that the spaces configuration will need to have the same spaceScope if they are both configured unless spaceScope is set to ALL.

You can find all the available Space Names by logging into your Atlassian account and then navigating to Confluence home --> Spaces --> View all spaces.

Basic authentication can be used with a username and password for on-premise Confluence or a personal access token (PAT) with token authentication.

A Confluence source can be configured to explicitly include and ignore certain spaces via the spaces and ignoreSpaces configuration keys respectively. These keys expect a list of Space Names (please note that the Space Name differs from the Space Key). For on-premises configuration, the endpoint can't contain atlassian.net.

Notes