The issue type selected is invalid. API 3 #18
Comments
|
I think i'm going to need some more information. It looks like it's selecting issuetype ID 11527. What I'm going to need to you do is save and run the following code: from tenable_jira.jira import Jira
from tenable_jira.config import base_config
from restfly.utils import dict_merge
import yaml, json
config_file = 'config.yaml'
config = dict_merge(
base_config(),
yaml.load(open(config_file), Loader=yaml.Loader)
)
jira = Jira(
'https://{}/rest/api/3'.format(config['jira']['address']),
config['jira']['api_username'],
config['jira']['api_token']
)
print('Issuetypes Selected are:')
for i in jira.issue_types.upsert(config['issue_types']):
print('{:>10}: {}'.format(i.get('jira_id'), i.get('name')))
print('Available Issue Types are:')
for a in jira.issue_types.list():
print('{:>10}: {}'.format(a.get('id'), a.get('name')))It should output something like this: Please reply with the results of the script. |
|
|
Multiple issuetypes named "Task" may likely be the issue. Not sure if they are the right IDs, but here is a stab at it... Can you add the following to your configuration file: issue_types:
- name: Task
jira_id: 12
type: standard
search:
- Tenable Plugin ID
- name: Sub-task
jira_id: 11200
type: subtask
search:
- Tenable Platform
- Tenable Plugin ID
- Tenable Asset UUID
- Device IPv4 Addresses
- Device IPv6 Addresses
- Vulnerability Port
- Vulnerability Protocol |
|
Thanks Steve, from the config.yaml I am seeing I might add this tio_severities:
- low
- medium
- high
- criticalis this the best approach to be able to pull in all the findings from the tenable platform ? |
|
it would actually be listed under the tenable section. so it would look like this: tenable:
tio_severities:
- low
- medium
- high
- critical |
|
Thanks Steve, tenable:
tio_severities:
- low
- medium
- high
- criticalat the top of the file and it's till only pulling the high and critical findings |
|
remember spaces are important. also you'll want to make sure that you merge this into the rest of your tenable section. it should look something like this all said and done: tenable:
platform: tenable.io
access_key: ACCESS_KEY_GOES_HERE
secret_key: SECRET_KEY_GOES_HERE
tio_severities:
- low
- medium
- high
- critical |
|
I'm very sorry. I'm not sure if I am doing something wrong the key values have been suppressed This results still in only pulling the high / critical events out |
|
I start python3 directly and then issued
|
|
can you enable debug logging so we can see what's being passed to the API? |
|
yes, I have a debug setting for the log but I am not sure what parts of the log file that you're hoping to see |
|
|
From the look of it, it appears to be working as expected: Note the severity parameter. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: