This documentation relates to the latest version of Confluence.
If you are using an earlier version, please go to the documentation home page and select the relevant version.

Delegate user management to use JIRA logins

All Versions

Confluence 3.0 Documentation

Index

If you already have a significant user base set up inside JIRA, it makes sense to connect Confluence to JIRA so that user management is centralised and not duplicated. This document outlines how to delegate Confluence's user authentication and group management to JIRA so that you can use your JIRA users to log in to Confluence.

Known Issues
Before attempting the steps below, please refer to the known issues listed in the troubleshooting section below.

On this page:

Read Before Proceeding

  1. The examples used in this document are based on Tomcat Application Server and the MySQL database. The same concepts (but not the verbatim examples) can be applied to other application servers or databases.

  2. If JIRA is using LDAP for authentication, you should not use JIRA for Confluence user management. Use Add LDAP Integration instead.

  3. Always install Confluence with a new database. Do not attempt to use the existing JIRA database, with either JDBC or data source.

  4. If you have existing users or groups in Confluence, these users will not be available once you switch to using JIRA's user management. Any existing content will no longer be associated with valid users. Do not add any spaces or content once Confluence installation is complete, apart from verifying that your Confluence instance is up and working, until you have completed the procedure on this page. Users in Confluence will no longer be valid once you switch over to using your JIRA users.

  5. If you run into a problem, check the Troubleshooting section below.

Technical Overview

In the configuration described below, Confluence will use JIRA's database for its user and group information. The Confluence application will have two database connections:

  1. A connection to the primary database, set up during Confluence installation. This database stores all the normal Confluence data: spaces, pages, comments, etc.
  2. A read-only data source connection to JIRA's database, set up after Confluence is installed. Confluence reads information about users and groups from this database.

The reason this works is because both JIRA and Confluence use the same user management library, OSUser. The OSUser database schema is the same in JIRA and Confluence, so Confluence can easily read from JIRA's tables to get the user and group information.

Step One: Installing Confluence

Skip this step if you have already installed Confluence and completed the Setup Wizard.

  1. Install Confluence and run the Setup Wizard:
    • If you are running JIRA standalone please follow these instructions for installing Confluence.
    • If you have JIRA deployed under your own Tomcat server, please follow these instructions.

  2. Ensure that Confluence is running and has been set up, that is, you have completed the Confluence Setup Wizard and verified that you can create pages.

  3. Shut down Confluence.

Step Two: Setting up a Datasource to JIRA's Database

In order to delegate all user authentication attempts and group membership queries to JIRA, Confluence needs to be aware of JIRA's database, and hence the user tables in JIRA's database.

In Tomcat this is achieved by specifying JIRA's database as a resource. You will need to declare it inside the <context> descriptor you set up in Step One.

Notes:

  • If there is an existing block of <Resource> in the <context> descriptor, please do not replace it. Rather, just add the following <Resource> block inside the <context> descriptor.
  • If you are running Confluence EAR/WAR edition separate to JIRA, or under JIRA standalone 3.3 and later, your Confluence context will be in the confluence.xml file.
    If you are running Confluence standalone separate to JIRA, or Confluence WAR/WAR edition under an older version of JIRA, your Confluence context will be in the server.xml file. You should never have a Confluence context in both.
  • If you are running Confluence standalone (or Confluence inside a JIRA standalone) and are not sure which version of Tomcat you are using, check your log files. You'll see *INFO: Starting Servlet Engine: Apache Tomcat/5.5.nn* if you are using Tomcat 5.5.
  • The DataSource configuration below uses MySQL as an example. You will need to modify these settings according to the database that you are using.
  • You should add the appropriate validation check for the connection pool to avoid intermittent problems authenticating.
Sample context descriptor for Tomcat 4.x and 5.0.x 
<Context path="/confluence" docBase="C:/programs/confluence" swallowOutput="true">
    <Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource"/>
    <ResourceParams name="jdbc/JiraDS">
    <parameter>
    <name>username</name>
        <value>your_db_username</value>
    </parameter>
    <parameter>
    <name>password</name>
        <value>your_db_password</value>
    </parameter>
    <parameter>
    <name>driverClassName</name>
        <value>com.mysql.jdbc.Driver</value>
    </parameter>
    <parameter>
    <name>url</name>
        <value>jdbc:mysql://your.domain.com/jira_database_name?autoReconnect=true</value>
    </parameter>
    <parameter>
        <name>factory</name>
        <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
    </parameter>
    </ResourceParams>
</Context>


Tomcat 5.5.x

This version of Tomcat has a new syntax for specifying resources. Note that you don't add a new context to server.xml, just add the Resource to your existing Context:

<Context path="/confluence" docBase="C:/programs/confluence" swallowOutput="true">
  <Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource"
     username="your_db_username"
     password="your_db_password"
     driverClassName="com.mysql.jdbc.Driver"
     url="jdbc:mysql://your.domain.com/jira_database_name?autoReconnect=true"/>
</Context>

Step Three: Installing the JDBC Driver

Ensure that your JDBC driver is on the classpath of your application server. In this example, a jar for the mysql driver should be in the .../common/lib folder (or potentially .../lib for Tomcat version 6 and beyond).

  1. Download the mysql driver from here.

  2. Copy the jar file into the .../common/lib folder (or .../lib).

Step Four: Modifying osuser.xml

Please make sure you have completed the Confluence Setup Wizard before performing this step.
  1. Find the osuser.xml file in the /confluence/WEB-INF/classes folder and open it in a text editor. Comment out the following block of code: 
    <provider class="bucket.user.providers.CachingCredentialsProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateCredentialsProvider</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>
    <provider class="bucket.user.providers.CachingAccessProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateAccessProvider</property>
        <property name="chain.configuration.provider.class">bucketuser.BucketHibernateConfigProvider</property>
    </provider>
    <provider class="bucket.user.providers.CachingProfileProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateProfileProvider</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>



  2. Uncomment this block: 
    <provider class="bucket.user.providers.CachingCredentialsProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcCredentialsProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
    </provider>
    <provider class="bucket.user.providers.CachingAccessProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcAccessProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
    </provider>
    <provider class="bucket.user.providers.CachingProfileProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcProfileProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>



    Your osuser.xml should now look like this:

    <opensymphony-user>
    <!--
		Authenticators can take properties just like providers.

		This smart authenticator should work for 'most' cases - it dynamically looks up
		the most appropriate authenticator for the current server.
	-->
    <authenticator class="com.opensymphony.user.authenticator.SmartAuthenticator"/>

    <!-- JIRA User management (with caching) -->
    <!-- Note: Do not add any line breaks or spaces when specifying the chain.classname, otherwise a ClassNotFoundException will be thrown -->

    <provider class="bucket.user.providers.CachingCredentialsProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcCredentialsProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
    </provider>
    <provider class="bucket.user.providers.CachingAccessProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcAccessProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
    </provider>
    <provider class="bucket.user.providers.CachingProfileProvider">
        <property name="chain.classname">com.atlassian.confluence.user.providers.jira.JiraJdbcProfileProvider</property>
        <property name="chain.datasource">java:comp/env/jdbc/JiraDS</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>

    <!--
    <provider class="bucket.user.providers.CachingCredentialsProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateCredentialsProvider</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>
    <provider class="bucket.user.providers.CachingAccessProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateAccessProvider</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>
    <provider class="bucket.user.providers.CachingProfileProvider">
        <property name="chain.classname">com.opensymphony.user.provider.hibernate.HibernateProfileProvider</property>
        <property name="chain.configuration.provider.class">bucket.user.BucketHibernateConfigProvider</property>
    </provider>
    -->

    <!--<provider class="com.opensymphony.user.provider.memory.MemoryCredentialsProvider" />
    <provider class="com.opensymphony.user.provider.memory.MemoryAccessProvider" />
    <provider class="com.opensymphony.user.provider.memory.MemoryProfileProvider" />-->
</opensymphony-user>

In this example, JiraDS is the name of the JIRA datasource you are sharing with Confluence. If you have changed the name in Step Two of this documentation, you will need change all occurrences of the value here too.

You can also download the already configured file here.

Step Five: Customising osuser.xml

In some cases you may need to customise the behaviour of the JiraJdbc classes. You can do this by setting properties within the osuser.xml file.

This process is documented here.

Step Six: Modifying atlassian-user.xml

This step is only applicable for Confluence 2.7 and later .

Please comment out or remove the following line from your <Confleunce-Install>/confluence/WEB-INF/classes/atlassian-user.xml file:

<hibernate name="Hibernate Repository" key="hibernateRepository"  description="Hibernate Repository" cache="true"/>

and add this line instead:

<osuser name="OSUser Repository" key="osuserRepository"/>

Step Seven: Creating Confluence Groups in JIRA

  1. Add the confluence-users and confluence-administrators groups in JIRA.

  2. Add yourself to both these groups.

  3. To give your existing JIRA users access to Confluence, you have two options.
    • Option 1: Manually edit the groups of these users inside JIRA and give them membership to one or both of these confluence groups.
    • Option 2: Start up Confluence. Log in using your JIRA account and go to Administration and then Global Permissions. Now assign the 'can use' permission to your desired JIRA groups.
      In order to use Confluence, users must be a member of the confluence-users group (or have Confluence 'can use' permission).

Step Eight: Activating External User Management

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 switch external user management on:

  1. Log into Confluence using your JIRA account.

  2. Go to the Administration Console and click General Configuration in the left-hand panel

  3. Click 'Edit' at the bottom of the 'Options and Settings' screen.

  4. Select 'ON' beside 'External User Management'.


For troubleshooting, see the JIRA Integration FAQ.

RELATED TOPICS
Delegate user management to use JIRA logins
Revert from JIRA to internal user management
Migrating users from Confluence to JIRA

Labels

user-management user-management Delete
confluence-jira confluence-jira Delete
jira-usermanagement jira-usermanagement Delete
jira jira Delete
confluence confluence Delete
user user Delete
management management Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (50)

 

  1. Jun 03, 2004

    Eric Hansen says:

    See http://jira.atlassian.com/browse/CONF-950. You apparently need to run throu...

    See http://jira.atlassian.com/browse/CONF-950. You apparently need to run through setup with external user management turned off. Wheh you finish setup, you can turn on external user management.

  2. Jan 28, 2005

    Nitin Chaumal says:

    Are there any pointers for integrating JIRA+Confluence into Weblogic/Jetspeed po...

    Are there any pointers for integrating JIRA+Confluence into Weblogic/Jetspeed portal and delegate the user management to these portals. This will help in having a single sign on for the entire portal not just JIRA+Confluence.

    You guys are doing a fantastic job.

  3. Jan 28, 2005

    Nitin Chaumal says:

    I completed this process successfully. I created a project in JIRA giving the li...

    I completed this process successfully. I created a project in JIRA giving the link to a confluence page for project documentation.
    I log into JIRA and click on this link but i am asked to login again.
    I also created a link on one of the confluence pages to a JIRA roject page, clicking on this link in confluence also takes me to the JIRA login page nstead of the project page. Is there a way to get over this.

    1. Feb 16, 2005

      Nick Faiz says:

      Hi Nitin, It's probably a good idea to shoot emails through to confluence-sup...

      Hi Nitin,
      It's probably a good idea to shoot emails through to confluence-support@atlassian.com , comments won't always have a timely response.

      Currently, we do not have single sign on between applications. While users can be shared across applications they must authenticate for each.

      Cheers,
      Nick

  4. Apr 11, 2005

    Anonymous says:

    The jira Context stuff in in the jira.xml file on my installation. Where would ...

    The jira Context stuff in in the jira.xml file on my installation. Where would the confluence context stuff then go?

    CHarlie

    1. Apr 18, 2005

      Anonymous says:

      you can create them in tomcat_home/conf/catalina/localhost

      you can create them in tomcat_home/conf/catalina/localhost

  5. Jun 16, 2005

    Jason Dillon says:

    Note, in the example to "uncomment this block": <provider class="bucket.p...

    Note, in the example to "uncomment this block":

    <provider class="bucket.providers.CachingProfileProvider">

    Should be:

    <provider class="bucket.user.providers.CachingProfileProvider">

  6. Jun 25, 2005

    Anonymous says:

    Are there any pointers for integrating JIRA+Confluence into Resin. I don't know ...

    Are there any pointers for integrating JIRA+Confluence into Resin. I don't know what will Tomcat <context> be in Resin!!!!

    1. Jul 01, 2005

      David Loeng says:

      The most crucial step in delegating user management is setting up a datasource i...

      The most crucial step in delegating user management is setting up a datasource in your Confluence webapp (regardless of what application server you are using) to point to JIRA's database.

      So in your resin.conf, you need a datasource that looks something like this: 

      <resource-ref>
    <res-ref-name>jdbc/JiraDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <init-param driver-name="org.postgresql.Driver"/>
    <init-param url="jdbc:postgresql://localhost/jiradb"/>
    <init-param user="postgres"/>
    <init-param password="postgres"/>
    <init-param max-connections="20"/>
    <init-param max-idle-time="30"/>
</resource-ref>

      Obviously you have to ensure that the appropriate JDBC drivers are in the classpath for your chosen application server too.

      The rest of the setup steps should be similar.

      Cheers,
      Dave

  7. Jul 05, 2005

    Barrow Kwan says:

    We are currently using LDAP for authentication ( basically it is just password c...

    We are currently using LDAP for authentication ( basically it is just password checking ). Can you do a mix of it ( JIRA/Confluence/LDAP ) ? ie Confluence will use JIRA's user database but authentication ( password checking ) will be done through LDAP?

    1. Jul 05, 2005

      Jens Schumacher says:

      Yes, that is possible. Simply follow the steps in [How to delegate user man...

      Yes, that is possible.

      Simply follow the steps in [How to delegate user management in Confluence to JIRA] and [Enable LDAP authentication] to setup this environment.

      1. Oct 26, 2006

        Buhi Mume says:

        Can somebody update the links? Thank you.

        Can somebody update the links? Thank you.

        1. Nov 21, 2006

          Ivan Benko says:

          Sorry about it Ldap integration Delegate User management to JIRA

          Sorry about it

          Ldap integration
          Delegate User management to JIRA

  8. Aug 22, 2005

    Jason shao says:

    Is it possible to take setup an install of Confluence with external user managem...

    Is it possible to take setup an install of Confluence with external user management, and then import data from an install which was not setup to delegate to JIRA?

    e.g. can I follow the direction above, then:

    • import a backup?
    • import a space at a time?
    • will it autocreate user entries?
    • will it overwrite existing user entries?

    1. Aug 23, 2005

      David Loeng says:

      Firstly, unless you intend this, importing a site backup from another install of...

      Firstly, unless you intend this, importing a site backup from another install of Confluence will wipe out everything in your current install.

      If you do intend this, user entries will not be autocreated in JIRA (remember the bridge from Confluence to JIRA is read only - Confluence cannot write to JIRA's user database).

      Space imports are fine.

      Cheers,
      Dave

      1. Sep 11, 2005

        Ricardo Sueiras says:

        If you have an existing Confluence setup and running, and you are deploying Jira...

        If you have an existing Confluence setup and running, and you are deploying Jira, but want to defer all user management to Jira (i.e. so there will be only one user profile, one place to mange permissions, etc) can you take all you existing users/groups/profiles from the confluence database, and import them into the jira user database?

        1. Sep 12, 2005

          Jens Schumacher says:

          You could transfer the users via a script or sql directly. However, you will hav...

          You could transfer the users via a script or sql directly. However, you will have to take care of the user email since the property set is stored in a different column in Jira. You will also have to join the user groups and add them into the jira database.

          Another way would be to create the users via the remote API. You will have to write a script which queries your database for the right data and creates the user in Jira via the remote API. The drawback there is that the user will have to change his password since there is no way to access and insert the current password.

          If you need any assistance with this task, please let us know and send an email to: confluence-support@atlassian.com

          Cheers,
          Jens

          1. Sep 12, 2005

            Ricardo Sueiras says:

            Thanks Jens. We will be using a custom authenticator so passwords will not be a...

            Thanks Jens.

            We will be using a custom authenticator so passwords will not be an issue, as the password stored in the database will not be used.

            When you say "join the user groups and add them into the jira database" what exactly do you mean? Do you mean add all the users into the "jira-users" group (or equiv) that is stored in the jira database?

            Thanks.

            1. Sep 12, 2005

              Jens Schumacher says:

              Ricardo, in order to keep the permissions set in Confluence working, you will h...

              Ricardo,

              in order to keep the permissions set in Confluence working, you will have to make sure that you move over all relationships between users and groups to your jira database.

              However, it is a little bit to complex to discuss this in the comment section of this page. Please write us an email to confluence-support@atlassian.com and we will happily assist you with the migration of your user database.

              Cheers,
              Jens

  9. Dec 15, 2005

    joe elliott says:

    Is there a particular reason that the first step of the directions specifically ...

    Is there a particular reason that the first step of the directions specifically say that the WAR version should be installed?

    I went through the whole process of setting up a clean Tomcat 5.5.12 instance, adding the Confluence webapp, etc.  It ran, but I quickly blew up with a Java out of memory error.  If there are any particular pointers in tuning a clean tomcat install, that would be nice.

    But irrelevant to that, I decided to just go back to my original standalone Confluence install and add the JiraDS config, and that seemed to work just fine.  (once i figured out that needed to use the Tomcat 4.x syntax for the data source config)

    1. Dec 15, 2005

      Jeremy Higgs says:

      Hi Joe, No, there's not particular reason that I know of. You should be able to...

      Hi Joe,

      No, there's not particular reason that I know of. You should be able to configure it with Confluence standalone with no problems.

      If you are getting OutOfMemoryErrors, have a look at [this page|http://confluence.atlassian.com/display/DOC/Memory+usage+and+requirements] on how to increase the amount of memory available to Confluence.

      Jeremy.

  10. May 02, 2006

    David Smiley says:

    It's nice to delegate the user management to Jira, but there is something missin...

    It's nice to delegate the user management to Jira, but there is something missing in this solution. If I don't delegate U.M., then when new users are added, they are automatically a member of the "confluence-users" group. In Jira, they are only in "jira-users" when a user is created. How can I get Jira to put the user in "confluence-users" too? I want my Confluence & Jira to be as "hands-off" (i.e. no administrator intervention) as possible.

    (This Confluence & Jira setup is within a corporate intranet whereas everyone is trusted.)

    I've thought of creating a database trigger but there is a concern that I don't know if it is a problem. The "id" attribute in Jira's database tables have no set default value. Presumably they are set by Jira and not the database (bad DB design IMO, but any way...). If my trigger were to choose the next highest ID, it's plausible there may be a conflict because Jira might have the highest id cached already.

    Atlassian, please offer some pointers.

    1. May 08, 2006

      David Zuttermeister says:

      Does giving  jira-users the 'can use' permission in Confluence solve your p...

      Does giving  jira-users the 'can use' permission in Confluence solve your problem?

      cheers,
      dz 

      1. May 09, 2006

        David Smiley says:

        Hmmm, that's an interesting idea. Can someone at Atlassian confirm that this te...

        Hmmm, that's an interesting idea. Can someone at Atlassian confirm that this technique will work fine? Some questions that come to mind:

        • Is "confluence-users" needed then?
        • Is there a template for new spaces so that I can ensure that the jira-users group has access?

        1. Jul 20, 2006

          David Ruhde says:

          In Jira, navigate to Administration, Global Permissions.  Add 'confluence-u...

          In Jira, navigate to Administration, Global Permissions.  Add 'confluence-users' to the"Jira User" permission.   All groups with "Jira User" permission are assigned to new users.

          1. Jul 21, 2006

            David Smiley says:

            Thanks, I didn't know about that.

            Thanks, I didn't know about that.

  11. Aug 29, 2006

    Jeffrey Silverman says:

    Allright, so, using these directions, I cannot get this to work. I have question...

    Allright, so, using these directions, I cannot get this to work. I have questions at every step of the instructions!

    "Step One: Installing Confluence"  It says "Preform installation against a new database...yadda yadda" Is that referring only to a "JIRA deployed under your own tomcat" installation? It seems like it is, but it might not be.

    "Ensure that Confluence is running" -- does this include going through the "Confluence setup wizard" or just seeing if Confluence brings up the setup wizard screen?

     "Step Two:..." It says, "In Tomcat..." but how can I tell which version of Tomcat? It is very unclear from the instructions here.  In fact, all of Step Two is unclear.

    Which version of Tomcat (I am running JIRA 3.6.2 standalone and Confluence 2.2.8 standalone)?  But I am trying to run Conflunce "under" JIRA.  In fact, I had that part working...

    Where do I specify the JDBC resource? In the Confluence installation config files? Or in the JIRA? I.e. I have a "server.xml" file(s) and a "confluence.xml" file(s) -- which do I use:

    ./jira/conf/server.xml

    ./confluence/conf/server.xml

    ./jira/conf/Catalina/localhost/confluence.xml

    "Step Three: JDBC Driver"

    Do I need to install the JDBC driver for Confluence? Or is having it in the JIRA installation enough?

    If yes, then where? Can I just copy the one from the JIRA install? 

    "Step Four: Modify OSuser"

    Well, first of all, there is a warning "Do this first!" which comes AFTER the whole set of instructions.  Hello? Put the warning FIRST! In any case, the warning is unclear.

    "Please perform this step after you have completed the Confluence setup wizard." Well, how? The Confluencee Setup Wizard has two options. Do I just choose "Standard Installation"? Well that doesn't make sense because I am going to use the JIRA database, aren't I?  Also, the "Wizard" has a configure user screen/step.  Why should I configure a user if I am going to be using all JIRA users anyways?

    So you can  see I am having rather a lot of difficulty.

    Here is my intended setup:

    JIRA Installed in /opt/jira  (WORKS)

    Confluence installed in /opt/confluence (Works if not connected to JIRA in any way)

    Configure JIRA to run on http://host.name:8080/ (Works!)

    Configure Confluence to run on http://host.name:8080/confluence (This worked too, until I tried to go past step one!)

    Thanks for any help here! 

    1. Sep 04, 2006

      Matt Ryall (Atlassian) says:

      Hi Jeffrey, Thanks for the feedback. We've made some updates to the document ab...

      Hi Jeffrey,

      Thanks for the feedback. We've made some updates to the document above, and followed this up with a support case.

      Please let us know if there's anything else we can help with.

      Regards,
      Matt

  12. Oct 26, 2006

    Buhi Mume says:

    I am trying to do the following: 1. Confluence to use LDAP only for authenticati...

    I am trying to do the following:
    1. Confluence to use LDAP only for authentication. (I have this working.)
    2. JIRA to use LDAP also only for authentication. (I have this working.)
    3. JIRA maintains its users and groups in its own database. (I have this working.)
    4. Confluence to utilize JIRA's database for the group management.

    On http://confluence.atlassian.com/x/Ugs, the first note says:

    1. If JIRA is using LDAP for authentication, you should not use JIRA for Confluence user management. Use Add LDAP Integration With Group Management instead.

    The refered page actually discusses using LDAP for user and group management, which unfortunately does not fit my need. Does anybody know how to solve the point #4 above?

    Thank you.

    1. Mar 11, 2008

      eugenelin says:

      I also need this function(#4 above).

      I also need this function(#4 above).

  13. Jun 02, 2008

    Craig Hannah says:

    Hi, I have successfully installed confluence-2.8.1-std and I am attempting to d...

    Hi,

    I have successfully installed confluence-2.8.1-std and I am attempting to delegate my user management to my atlassian-jira-enterprise-3.12.3-standalone application. 

    I want to minimize the permissions I give to the jiraDS datasource user. If I grant all privileges on all objects to the id the datasource uses, it works fine. However if I just give it select, it fails. I can find no log message anywhere that would give me a hint as to what access it needs.

    Can anyone tell me what Jira tables are needed and what with what privileges? (This is Oracle 10g on Solaris)

     Thanks,

    Craig 

    1. Jun 06, 2008

      Fennie Ng says:

      Hi Craig, Please raise a support ticket at : https://support.atlassian.com ...

      Hi Craig,

      Please raise a support ticket at :

      and attach the <Confluence-Home>/logs to the support ticket.

      Regards,
      Fennie

  14. Jun 05, 2008

    Andrew Holmes says:

    Argh. I'm officially frustrated. I've installed 2.8.1 standalone separately from...

    Argh. I'm officially frustrated. I've installed 2.8.1 standalone separately from our Jira standalone. I am now at the point where:

    1. If I point Confluence to use Jira users, then my login to Confluence requires a different password than for Jira. However, I see the Jira profile for myself once in Confluence.

    2. If I point Confluence NOT to use Jira users, then everything works, BUT -- forgetting to turn off external user management causes Confluence to use the Jira password (!), even though the configs don't point to the Jira users. Very bizarre.

    3. Either way, having Confluence and Jira open in separate Firefox windows or tabs logs me out of Jira every time I do something in Confluence, and vice versa. Unusable with this behavior, which doesn't happen in separate windows with IE.

    Can someone comment on my #1 and/or #2 situations? Does anyone have this working well with separate standalone instances?

     Thanks,

    Andy Holmes

    1. Jun 09, 2008

      Tony Cheah Tong Nyee says:

      Hi Andrew, There may have many factors come into play in this case. I would sug...

      Hi Andrew,

      There may have many factors come into play in this case. I would suggest you to raise a support request regarding this in our Support System:

      From there we will help to investigate further. It may be helpful if you could attach the configuration file and outline the steps taken in detail on how did you integrate Confluence with JIRA users on the support issue.

      Cheers,
      Tony

    2. Jun 11, 2008

      Craig Hannah says:

      Hi Andy, I can comment on your third issue as I am experiencing the same sympto...

      Hi Andy,

      I can comment on your third issue as I am experiencing the same symptoms. I have Jira & confluence stand-alone implementations on the same machine. Any action in a browser window for one destroys the session for the other. It appears that the problem is that both products are using a cookie name of 'jsessionid' to maintain their state. Since both Jira & confluence are on the same host, and in my case are both the root context (on different ports) they overwrite each other.

      In searching through Atlassian's support tickets I see this problem reported in a number of places (CONF-799*,*  JRA-14968 and more). the suggestion of http://jira.atlassian.com/browse/JRA-11915 is to not have them as the root context. They will then be distinguished by the host name.

      Good luck,

      Craig 

  15. Jun 13, 2008

    Anonymous says:

    Hi, I am implementing single sign on feature of confluence and JIRA. I am using...

    Hi,

    I am implementing single sign on feature of confluence and JIRA. I am using the following link for that:

    http://confluence.atlassian.com/display/DOC/Delegate+user+management+to+use+JIRA+logins

    But I am facing problem with these steps :

    - when i modify the osuser.xml file and switch from hibernate to osuser framework I am not able to to access the confluence page .
    - for the next step i.e eight when i try to access the confluence with my jira link i get message that username and pwd is not right?
    I am accessing the confluence through link : http://localhost:<jira-port-no>/confluence ... i get the confluence login page but i am not able to login again ?

    please explain the eight step where it suggests to login into confluence with jira username and pwd....
    - at that time wht shud i do....which service shud be started..jira or confluence ?

    - how to login in confluece which link we shud use..is it jira one or conflucence one

    or we shud use this link as http://localhost:<jira-portno>/confluence

    Please help me .. I am very confused and tried this step several times but i wasnt able to login into the confluence with jira username and password. I have followed all the above steps of the delegate user management but still i think i am missing something...... please help..

    Thanks,
    Shrikant

    1. Jun 17, 2008

      Mei Yan Chan says:

      Hi Shrikant, Please raise this issue in our support system at: https://suppo...

      Hi Shrikant,

      Please raise this issue in our support system at:

      Thanks.

      Regards,
      Mei

      1. Feb 14

        Anonymous says:

        I'm having the same problem.  Was an issue opened for this?  If so, is...

        I'm having the same problem.  Was an issue opened for this?  If so, is there any thing I can look at for a possible solution? Thanks

        1. Feb 14

          Anonymous says:

          Never mind me.  I got it working.  I had used the wrong user/name pass...

          Never mind me.  I got it working.  I had used the wrong user/name password in the <context><resource> for the data provider database.  Oddly, there was no error information in the logs.

  16. Nov 14, 2008

    Anonymous says:

    If you use SQL Server and encounter the error java.sql.SQLException: Invalid ob...

    If you use SQL Server and encounter the error

    java.sql.SQLException: Invalid object name 'userbase'.

    See http://confluence.atlassian.com/display/KB/CSP-19533+-+Delegating+user+management+to+use+Jira+logins+does+not+function+(Invalid+Username+or+Password)

  17. Feb 11

    Chris Gibbs says:

    Does this assume that the Public Signup feature is set to OFF in Confluence? or ...

    Does this assume that the Public Signup feature is set to OFF in Confluence? or is it possible to keep that feature on with this setup?

    1. Feb 18

      Azwandi Mohd Aris says:

      Hi Chris, Once you have delegated user management to JIRA, the public signup wi...

      Hi Chris,

      Once you have delegated user management to JIRA, the public signup will not work (throws an error message). Therefore, we recommend administrators to perform the "Step Eight: Activating External User Management". This will turn off all the user management options in Confluence to avoid anyone from using them.

      Cheers,
      Azwandi

      1. Feb 18

        Chris Gibbs says:

        Activating external user management in Confluence 2.10.1 does not disable or aut...

        Activating external user management in Confluence 2.10.1 does not disable or automatically turn off the "Public Signup" feature (see screen capture). You are correct though in that if the Public Signup is left ON and someone tries to sign up there will be an error thrown. Unless I'm missing something, it should be noted in step eight to also ensure that Public Signup is set to OFF.

        1. Feb 18

          Kevin Mills says:

          I can verify this as I just ran into it myself.

          I can verify this as I just ran into it myself.

          1. Feb 26

            Azwandi Mohd Aris says:

            Hi all, Indeed, I can verify that this problem happens in the recent versions o...

            Hi all,

            Indeed, I can verify that this problem happens in the recent versions of Confluence. I have created a regression bug report at http://jira.atlassian.com/browse/CONF-14708. Feel free to watch it.

            Cheers,
            Azwandi

  18. Jun 26

    Richmond-rae Dalisay says:

    Salutations, Just an observation. when I tried this approach and login to JIRA ...

    Salutations,

    Just an observation. when I tried this approach and login to JIRA as an Admin, it seems that may change password setting is missing in my Preference. Also, the same with the other users, when I tried to check the userlist in the Admin section, it seems that all of the user's change password option is missing.

    Is this a bug or the consequence of using this approach?

    How do I resolve this? How do I change my password?

    Thanks in advance.

    1. Jun 28

      Richmond-rae Dalisay says:

      Salutations, Found the solution in my problem. Thanks.

      Salutations,

      Found the solution in my problem.

      Thanks.

    2. Jun 30

      sashidaran jayaraman [Atlassian] says:

      Hi Richmond-rae Dalisay, This would be the consequence of using this approach a...

      Hi Richmond-rae Dalisay,

      This would be the consequence of using this approach as indicated here. Ensure that the External User Management is activated on Confluence and not in JIRA.

      Hope this helps.

      Cheers
      JSashi

  19. Jun 29

    Anonymous says:

    Nick, on Feb 16, 2005 you stated: Currently, we do not have single sign on betwe...

    Nick, on Feb 16, 2005 you stated:

    Currently, we do not have single sign on between applications. While users can be shared across applications they must authenticate for each.

    Is this still true?

    Regards
    Jan

    1. Jun 30

      sashidaran jayaraman [Atlassian] says:

      Hi Jan, Yes, this is still true. However, Atlassian has come up with Crowd, whi...

      Hi Jan,

      Yes, this is still true. However, Atlassian has come up with Crowd, which implements Single Sign On (SSO) for as many users, web applications and directory servers as needed. For more information on Crowd, you can refer here

      If you happen to encounter issues regarding Crowd, you could raise support ticket at Atlassian Support

      Hope this helps.

      Cheers
      JSashi

Add Comment


Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.