Confluence
for Atlassian Confluence.
In order to configure Confluence, you need to be able to create a token.
You can configure this source to run through the integration wizard on the frontend or you can use a local configuration file as outlined below.
Basic authentication with an email address for the username and a Confluence cloud token for the password must be configured using basic authentication for Confluence Cloud.
You can use a username and password with basic authentication, or you can use 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).
Key | Description | Required |
endpoint | The target endpoint URI | Yes |
spacesScope | Scope for retrieving all spaces. Values can be ALL, GLOBAL or PERSONAL | No |
insecureSkipVerifyTls | Boolean to skip TLS/SSL verification for insecure connections | No |
spaces | Array of spaces to be included for retrieval. Omit to enumerate instead. | No |
ignoreSpaces | Array of spaces to be ignored during retrieval | No |
includeAttachments | Boolean to include attachments during retrieval | No |
skipHistory | Boolean to skip retrieval of historical data | No |
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).
Feature | Supported |
Scan archive files | ✅ |
Scan attachments | ✅ |
Scan base64 encoded data | ✅ |
Scan binaries | ✅ |
Comments | ❌ |
Exclude Filter | ✅ |
Auto resume | ✅ |
Scan version history | ✅ |
Notes
- Attachment scanning is opt-in; version/history scanning is opt-out