Confluence

enterprise feature this feature is only available with trufflehog enterprise contact us to learn more {{source}} for atlassian confluence configuration in order to configure confluence, you need the ability to create a token web configuration you can configure this source through the integration wizard on the frontend or you can use a local configuration file as outlined below local configuration the confluence integration supports basic authentication (for both confluence cloud and confluence datacenter and server ) bearer token (only for confluence datacenter and server ) confluence cloud 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 confluence cloud basic auth sources \ connection '@type' type googleapis com/sources confluence endpoint https //ourbusiness atlassian net/wiki basicauth \# username for confluence cloud must be an email username scanner account\@ourbusiness com \# password for confluence cloud must be an access token password xxxxxxxxxxxxxxxxxxxxxxxxxx spaces \ test space \ future projects space ignorespaces \ space1 includeattachments true skiphistory true spacesscope all name confluence scanperiod 12h type source type confluence verify true confluence datacenter and server 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 basic auth sources \ connection '@type' type googleapis com/sources confluence endpoint https //ourbusiness com/wiki basicauth username scanner account password xxxxxxxxxxxxxxxxxxxxxxxxxx spaces \ test space \ future projects space ignorespaces \ space1 includeattachments true skiphistory true spacesscope all name confluence scanperiod 12h type source type confluence verify true access token sources \ connection '@type' type googleapis com/sources confluence endpoint https //ourbusiness com/wiki token xxxxxxxxxxxxxxxxxxxxxxxxxx spaces \ test space \ future projects space ignorespaces \ space2 includeattachments true skiphistory true spacesscope all name confluence scanperiod 12h type source type confluence verify true options 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 capabilities 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