jhonny606
commented
1 year ago Config.yaml:
tenable:
# Tenable.io or API Access Key
access_key: ********
# Tenable.io or API Secret Key
secret_key: ********
jira:
# The API Token to use to authenticate to the Jira application
api_token: ************
# The User that will be authenticaing to the Jira application
api_username: ************
# The address pointing to the Jira application.
address: ******.atlassian.net
project:
# The lead account id for the primary user for the project.
leadAccountId: ***********
# The following log definitions are optional. Only specify these if you want
# to change the default logging behavior of only outputting warnings and errors
# to the screen.
log:
# What is the logging level desired? Available levels are:
# debug, info, warn, error
# The default level if unspecified is "warn"
level: debug
# If you would like the log output to goto a file instead of standard output,
# then specify the filename here:
filename: *******/logfile.log
# The following section is optional. You should only specify this section if
# you would like the bridge to run as a service with it's own timer.
service:
# How many hours should we wait between jobs? Note setting this to a
# non-zero number will result in imports past the initial import will use
# time of the last completed import as the basis for last observed.
interval: 1
screen:
jira_ids:
- 10139
- 10140
- 10016
- 10017
quantumuser23
I did the integration, and when I run the command tenable-jira config.yaml it imports Tenable vulnerabilities into Jira. So far so good. However, when correcting a vulnerability, instead of closing or completing the issue (updating its status) it duplicates/creates a new issue in Jira, and does not resolve the issue, even if the vulnerability is listed as fixed in Tenable. Can you help?