Jira

jira edition enterprise only the jira integration scans issue descriptions, comments, and attachments in atlassian jira for credentials and other sensitive data to send trufflehog detections to jira as notifications, see the jira notifier instead configuration the jira integration can be configured in trufflehog under integrations , or via a local configuration file (below) web configuration configure this integration from the integrations page in trufflehog you'll need credentials appropriate to your jira deployment — see the local configuration section below for the supported authentication methods local configuration local configuration supports three authentication modes, depending on your jira deployment jira cloud (basic auth) — uses your atlassian email address as the username and a jira cloud api token as the password jira server / data center (bearer token) — uses a personal access token (pat) jira server / data center (basic auth) — uses an account username and password if projects is omitted, all projects the credentials can list and access are scanned jira cloud (basic auth) use this for jira cloud the username must be the email address attached to your atlassian account, and the password must be a jira cloud api token standard passwords cannot be used in place of an api token for jira cloud sources \ connection "@type" type googleapis com/sources jira endpoint https //ourbusiness atlassian net basicauth \# jira cloud requires an api token for the password username scanner account\@ourbusiness com password xxxxxxxxxxxxxxxxxxxxxxxxxx name jira scanperiod 12h type source type jira verify true jira server / data center (bearer token) use this for self hosted jira with a personal access token sources \ connection "@type" type googleapis com/sources jira endpoint https //jira ourbusiness com token xxxxxxxxxxxxxxxxxxxxxxxxxx name jira scanperiod 12h type source type jira verify true jira server / data center (basic auth) use this for self hosted jira with username and password authentication sources \ connection "@type" type googleapis com/sources jira endpoint https //jira ourbusiness com basicauth username scanner account\@ourbusiness com password xxxxxxxxxxxxxxxxxxxxxxxxxx projects \ eng \ itsys name jira scanperiod 12h type source type jira verify true configuration options field type required description endpoint string yes the url of the jira instance projects list no explicit list of project keys to scan omit to enumerate instead ignoreprojects list no project keys to skip during scanning combines with enumeration insecureskipverifytls boolean no skip tls certificate verification setting this to true may pose security issues capabilities feature supported scan issue descriptions ✅ scan comments ✅ scan attachments ✅ scan archive files ✅ scan base64 encoded data ✅ scan binaries ✅ auto resume ✅