Configuring JIRA Integration in the Setup Wizard
This page describes the Connect to JIRA step in the Confluence setup wizard.
If you are already using a JIRA application, you can choose to delegate user management to JIRA, instead of separately maintaining your users in Confluence.
You'll be able to specify exactly which groups in your JIRA app should also be allowed to log in to Confluence. Your license tiers do not need to be the same for each application.
It's possible to connect Confluence to JIRA after completing the setup process, but it's much quicker and easier to set it up at this stage.
You can delegate Confluence's user management to:
- JIRA 4.3 or later
- JIRA Core 7.0 or later
- JIRA Software 7.0 or later
- JIRA Service Desk 3.0 or later.
Connecting to a JIRA application in the Setup Wizard
Enter the following information:
JIRA Base URL - the address of your JIRA server, such as
- JIRA Administrator Login - this is the username and password of a user account that has the JIRA System Administrator global permission in your JIRA application.
Confluence will also use this username and password to create a local administrator account which will let you access Confluence if JIRA is unavailable. Note that this single account is stored in Confluence's internal user directory, so if you change the password in JIRA, it will not automatically update in Confluence.
- Confluence Base URL - this is the URL JIRA will use to access your Confluence server. The URL you give here overrides the base URL specified in Confluence, for the purposes of connecting to the JIRA application.
- User Groups - these are the JIRA groups whose members should be allowed to use Confluence. Members of these groups will get the 'Can use' permission for Confluence, and will be counted in your Confluence license. The default user group name differs depending on your JIRA version:
- JIRA 6.4 and earlier:
- JIRA Software 7.x and later:
- JIRA Core 7.x and later:
- JIRA Service Desk 3.x and later:
- JIRA 6.4 and earlier:
- Admin Groups – Specify one or more JIRA groups whose members should have administrative access to Confluence. The default group is
jira-administrators. These groups will get the system administrator and Confluence administrator global permissions in Confluence.
If you have trouble connecting Confluence to JIRA, the following troubleshooting information should help you get up and running.
If no users can log in to Confluence after you've completed the setup process, check that the people are members of the JIRA groups you specified. Only members of these groups will get the 'Can Use' Confluence permission.
|Error in the setup wizard||Cause||Solution|
Failed to create application link, or
Failed to authenticate application link
|The setup wizard failed to complete registration of the peer-to-peer application link with JIRA. JIRA integration is only partially configured.||Follow the steps below to remove the partial configuration then try the Connect to JIRA step again.|
|Failed to register Confluence configuration in JIRA for shared user management||The setup wizard failed to complete registration of the client-server link with JIRA for user management. The peer-to-peer link was successfully created, but integration is only partially configured.||Follow the steps below to remove the partial configuration then try the Connect to JIRA step again.|
|Error setting Crowd authentication||The setup wizard successfully established the peer-to-peer link with JIRA, but could not persist the client-server link for user management in your
||Fix the problem that prevented the application from saving the configuration file to disk then follow the steps below to remove the partial configuration before trying the Connect to JIRA step again.|
|Error reloading Crowd authentication||The setup wizard has completed the integration of your application with JIRA, but is unable to start synchronizing the JIRA users with your application.||
Restart Confluence. You should be able to continue with the setup wizard. If this does not work, contact Atlassian Support for help.
java.lang.IllegalStateException: Could not create the application in JIRA/Crowd (code: 500)
The setup wizard has not completed the integration of your application with JIRA. The links are only partially configured. The problem occurred because there is already a user management configuration in JIRA for this <application> URL.
|Follow the steps below to remove the partial configuration and resolve any conflict with existing links then try the Connect to JIRA step again.|
Removing a partial configuration
If you hit a roadblock, you'll need to log in to JIRA and remove the partial integration before you can try again. The specific steps will differ depending on your JIRA application and version, but the essentials are the same for all versions:
- Log in to JIRA as a user with system administrator permissions.
- In the Administrator screens, go to Application Links.
- Remove the application link that matches the base URL of your Confluence server.
- In the User Management screens, go to JIRA User Server.
Remove the link that matches the name and base URL of your Confluence server from the list of applications that can use JIRA for user management.If you have multiple servers running on the same host...
If you're unable to tell which link matches your Confluence server because you have multiple servers of the same type running on the same host you can check the application ID, which is listed beside each server.
To find out the application ID of your new Confluence site, go to
<baseurl>is the base URL of your Confluence site). The application ID will be listed in the
- Return to the Confluence setup wizard and try the Connect to JIRA step again.
If you're still unable to connect JIRA and Confluence using the setup wizard, you may need to skip this step and set up the links between JIRA and Confluence manually once you've completed the Confluence setup process. See Connecting to Crowd or JIRA for User Management.
Note about trusted applications authentication
When you connect to a JIRA application in the setup wizard, the setup procedure will configure Trusted Applications authentication for your application. Please be aware of the following security implications:
- Trusted applications are a potential security risk. When you configure Trusted Applications authentication, you are allowing one application to access another as any user. This allows all of the built-in security measures to be bypassed. Do not configure a trusted application unless you know that all code in the application you are trusting will behave itself at all times, and you are sure that the application will maintain the security of its private key.
- Only use Trusted Applications authentication if both your servers have the same set of users and the servers fully trust each other.
Was this helpful?
Thanks for your feedback!