Troubleshooting and Frequently Asked Questions
The following are some common errors and questions users may encounter when configuring and managing mobilization initiatives.
How long does it take to see initiative/ticket data?
For initiatives created within Tenable One Vulnerability Management:
-
Newly created initiatives and their data appear in the user interface within minutes.
-
Existing initiatives automatically update once every 24 hours, or when there is a change to the initiative scope that triggers on-demand metric recalculation.
Tip: In Tenable One Vulnerability Management, you can view the time at which an initiative's metrics were last calculated in the Initiative Overview section. -
Due to data caching policies, the following project-related updates made within Jira can take up to an hour to appear within Tenable One Vulnerability Management:
-
List of projects
-
Project details
-
Users with access to a project
-
Issue types for a project
-
Priority schemes
-
For tickets created within Tenable Exposure Management:
-
It can take up to 10 minutes to see the newly created and updated ticket information in both Tenable Exposure Management and the ticketing system.
How can I debug issues with my configuration?
Tenable recommends regularly monitoring the Activity Logs. These logs provide real-time visibility into the status and execution of your third-party ticketing integration configurations, allowing you to verify successful data synchronization and quickly identify any communication failures between platforms.
Tenable logs the following mobilization-related actions:
| Action | Description |
|---|---|
| mobilization.ticket.create | The user created an initiative linked to their third-party ticketing integration. |
| mobilization.ticket.update | The user made an update to an initiative linked to their third-party ticketing integration. |
| mobilization.ticket.delete | The user deleted an initiative linked to their third-party ticketing integration. |
| mobilization.ticket.poll | Tenable checked the status of a ticket in the linked third-party ticketing integration. |
To view your activity logs:
-
Log in to Tenable One Vulnerability Management.
-
In the left navigation menu, click
Settings.
The Settings page appears.
-
Click the Activity Logs tile.
The Activity Logs page appears. This page shows a list of activities associated with your organization's Tenable Vulnerability Management account.
-
In the Search text box, type "mobilization".
The list automatically filters for audit log events related to your mobilization configuration.
-
Review the results and check the Description column for any errors that can be fixed.
Why are tickets not created even though my integration shows as connected?
Ticket creation is an asynchronous process, so Tenable cannot display ticket creation errors in the user interface. A Connected status confirms only that Tenable can reach your ticketing system. It does not confirm that the integration user can create tickets in the project you selected.
If tickets are not appearing, do the following:
-
Review the Activity Logs for failed mobilization.ticket.create actions. For more information, see How can I debug issues with my configuration?.
-
Confirm the Jira user meets the Prerequisites, including the required permissions and project fields.
-
Confirm the Jira project allows the fields Tenable sends, such as assignee, labels, parent, and reporter.
Which Jira settings commonly cause ticket creation to fail?
| Issue | Resolution |
|---|---|
| The integration user cannot be assigned tickets, or the assignee you selected is not valid for the project. | In Jira, confirm the user has the ASSIGNABLE_USER permission in the project, and that the integration user has the ASSIGN_ISSUES permission. |
| The project does not include a required field, such as priority, labels, or parent. | In Jira, add the missing field to the screens and field configuration for the project's issue types. |
| The ticket's reporter cannot be set. | In Jira, grant the integration user the MODIFY_REPORTER permission. |
| Tickets are created but their status does not update. | In Jira, confirm the integration user has the EDIT_ISSUES and LINK_ISSUES permissions, and that the project allows tickets to transition to the Done status. |
Why do I see a "no permission to view statuses" error for Jira?
To retrieve the statuses for a Jira project, the Jira user who authorizes the connection must have project administrator access to that project. A global Jira administrator is not required. If the user has only project member permissions, Tenable cannot read the project's statuses.
To resolve the error, in Jira, assign the user the Administrator role in the project. For more information, see Prerequisites.
What happens when an OAuth connection expires or access is revoked?
For both Jira and ServiceNow, Tenable renews an expired access token automatically and retries the operation. Jira refreshes its token, and ServiceNow obtains a new token using its client credentials. If renewal succeeds, you do not need to take any action.
If renewal fails or access is revoked, ticket creation can fail, and the connector page shows the connector status as Disconnected. To restore the connection, do the following:
-
Jira — Recreate the connector. For more information, see Configure Jira.
-
ServiceNow — In ServiceNow, restore the OAuth application's access, or in Tenable, update any invalid client credentials.
How do I troubleshoot OAuth connection problems?
OAuth scopes do not replace the permissions of the user who authorizes the connection. For Jira, the user needs the relevant project permissions and project administrator access. For ServiceNow, the OAuth application user needs at least the itil or incident_manager role and the rest_service role.
| Issue | Resolution |
|---|---|
| Jira: Atlassian shows an error page, and the authorization popup does not return. | The callback URL in your Jira OAuth 2.0 (3LO) app does not match the one on the Tenable connector form. Copy the callback URL from the connector form exactly. |
| Jira: Connector setup returns an error about scopes or the Cloud ID. | Setup validates both. Add any missing scopes to your Jira app or correct the Cloud ID, and then repeat the authorization. |
| ServiceNow: The connection fails. | Confirm the OAuth application is active, and that the client ID, client secret, and instance URL are correct. |
| ServiceNow: An operation fails after authentication succeeds. | Check the application user's roles and any table or label access control lists (ACLs) that your instance requires. A persistent authentication error can also mean that access was revoked. |
Why am I unable to create tickets manually?
Only Tenable administrators can create tickets manually from the Findings page. If you do not see Create Jira Ticket or Create ServiceNow Ticket in the Take Action menu, ask an administrator to create the ticket for you.
