Confluence 2.6 : How to delegate user management in Confluence 1.0 to JIRA
This page last changed on Sep 14, 2006 by david.soul@atlassian.com.
This version of the document applies to Confluence 1.0 and earlier. Users of Confluence 1.0.1 and later should refer to this document instead. This article will help you set up Confluence to re-use your existing JIRA user base. The examples assume you are running Confluence under Tomcat 4.1.x and your JIRA database is running under Postgres, but the same concepts (but not the verbatim examples) can be applied to other application-servers or databases. Please note that this feature will not work if you are using JIRA with the embedded HSQL database. That is, this will not work if you are running JIRA standalone against the default database out of the box. However, it does not matter which database you are using for Confluence. Step 1 - Run through standard setup process
Note: the admin user account will no longer be valid once you switch over to using your JIRA user base. Therefore you should avoid adding any content with this account. Step 2 - Set up datasource to JIRA user base
You will need to change the sample values given above to suit your installation. Step 3 - Install JDBC driver in Tomcat
Step 4 - Modify osuser.xml
Step 5 - Create Confluence Groups in JIRA
To give your existing JIRA users access to Confluence, you have two options.
In order to use Confluence, users must be a member of the confluence-users group (or have confluence USE permission). Step 6 - Activating External User ManagementFinally, since user management is now conducted in JIRA and outside of Confluence, you will need to switch external user management on. Activating external user management will remove user and group management options from Confluence. Your users will also no longer be able to edit their full name or email address inside Confluence (if they want to, they would have to do so in JIRA). To do this:
|
![]() |
Document generated by Confluence on Oct 10, 2007 18:47 |