This article provides instruction for configuring Discovery Center to interact with the Jira and Confluence platforms, including on-premise and in the cloud instances.
See the latest Connectors Compatibility Summary for the latest state of features for this connector.
Atlassian configuration
Support
The Discovery Center Jira Connector supports cloud instances, as well as on-premise instances using Jira Core Rest APIs Versioned 7.6.1 and up.
Similarly, the Confluence connector supports cloud instances, as well as on-premise instances using version 6.12.1 and up.
Authentication
In order to access content, an account must be provided which has access to these repositories.
The account requires unrestricted access to pages (Confluence), issues (Jira), and their associated attachments in order to discover and analyze the content. Our recommendation is that users with the System Administrator role in these systems are considered for use when connecting to either repository.
With on-premise deployments, authentication is handled using basic authentication with a username and password.
With cloud deployments, authentication is handled using an email address and an API token. See below for instructions on obtaining an Atlassian API token. https://confluence.atlassian.com/cloud/api-tokens-938839638.html
Discovery Center Configuration
Credential Management
Follow the steps below to set up credentials within Discovery Center
- Navigate to the credential management section of Discovery Center found under "System Settings"
- Create a new credential to be used for your Jira or Confluence connection.
For on-premise connections, use the username and password credential type, and fill in the relevant fields. For cloud connections, use the username and password credential type, filling the username field with the account's email address, and the password field with the account's API token.
Network Map
Follow the steps below to set up a location within Discovery Center
- Navigate to the Network Map tab.
- Add a new location.
- Start the location with the relevant prefix such as "jira://" or "confluence://" in the section labeled "Path".
- Complete the path field by filling in your relevant address.
- For Cloud Confluence instances, you must add your location until the spaces node at a minimum.
ie. 'confluence://confluenceserver.atlassian.net/wiki/spaces'. - If you intend to add at a lower level with Jira, you must structure the start location to match the necessary virtual directory structure.
ie.
- jira://jiraserver.atlassian.net:443/software/
- jira://jiraserver.atlassian.net:443/software/E/
- jira://jiraserver.atlassian.net:443/software/E/ExampleProject/ - In cases where you have used a custom port, append a colon along with that port number to the server.
ie. confluence://confluenceserver.com:54321/ - Select the relevant Connector type in the second dropdown labeled "Location Type"
- Select the credentials we created earlier in the third dropdown labeled "Credentials"
- Save
Common issues
Discovery Center may fail to interact with on-premise instances of Jira or Confluence if the associated certificate is not valid. If you encounter errors indexing an on-premise instance of Jira or Confluence, double-check that the certificate for that repository is still valid and is installed where necessary.
By default, the connector only supports HTTPS local instances and will fail if your instance of Jira or Confluence runs on HTTP. If you must access these repositories via HTTP, please open a support ticket with the ActiveNav support team.