Site announcement

We are switching off article comments on this website. Read about the upcoming changes to Atlassian Documentation.

Documentation for Crowd 2.8. Documentation for earlier versions of Crowd is available too.

Skip to end of metadata
Go to start of metadata

If you have already been using Atlassian JIRA, and are now configuring JIRA as a Crowd application, you will probably want to import your existing JIRA users and groups into a Crowd directory.

It is recommended that you import your JIRA users into an Internal Directory that has its 'Password Encryption' set to 'ATLASSIAN-SECURITY'. Otherwise, users' passwords will not be copied across to Crowd.

To import users and groups from Atlassian JIRA into a Crowd directory,

  1. Ensure that the database drivers for the JIRA database are on Crowd's classpath. To do this, simply copy the JDBC driver jar for your particular JIRA database across to apache-tomcat/common/lib in your Crowd installation directory. Then restart Crowd.
  2. Log in to the Crowd Administration Console.
  3. Click the 'Users' link in the top navigation bar.
  4. This will display the User Browser. Click the 'Import Users' link.
  5. This will display the 'Import Type' screen. Click the 'Atlassian Importer' button.
  6. This will display the 'Options' screen. Complete the fields as follows:
    • 'Atlassian Product' — Select 'JIRA'.
    • 'Directory' — Select the directory that you have created for your JIRA users.
    • 'Import Passwords' — Select this checkbox if you wish to import the users' passwords from JIRA. You can only import passwords if the Crowd directory is using the 'Atlassian SHA1' encryption method.
    • 'Product Database URL' — Type the URL of your JIRA instance's database. The exact syntax will depend on which database you are using; see Connecting JIRA to a Database in the JIRA Installation Guide.
    • 'Database Driver' — Type the name of your JIRA instance's database JDBC driver, e.g.
      • For MySQL, type  com.mysql.jdbc.Driver

      • For PostgreSQL type org.postgresql.Driver

      • For Oracle type oracle.jdbc.OracleDriver
      • For MS SQL Server type net.sourceforge.jtds.jdbc.Driver
      • For HSQLDB type org.hsqldb.jdbcDriver
    • 'Username' — Type the username of the database user that Crowd will use to log in to your JIRA instance's database.
    • 'Password' — Type the password of the database user Crowd will use to log in to your JIRA instance's database.
      (info) The import process will log in to the database, not into JIRA.
  7. Click the 'Continue' button to import the users from your JIRA instance into your Crowd directory.
  8. The 'Results' screen will be displayed, showing how many users and groups have been imported into your Crowd directory.
  9. Click the 'Users' button to view and manage the imported users and groups via the Crowd Administration Console (assuming the directory's permissions allow this).

Screenshot: 'Import JIRA Users'

Next Step

To give the imported groups access to the JIRA application, see Specifying which Groups can access an Application.

RELATED TOPICS

Crowd Documentation  

6 Comments

  1. Hi All,

    If you are facing this problem while importing users:

    This is a known bug, please apply the patch to solve this problem. This bug is going to be fixed on Crowd version 2.2.7, 2.3.

    Thanks

  2. If you are seeing this error message from the log file when importing the users and connecting to MS SQL server:

     org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT groupname from groupbase order by groupname]; nested exception is java.sql.SQLException: Invalid object name 'groupbase'.
    at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:220)
    ....
    Caused by: java.sql.SQLException: Invalid object name 'groupbase'.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

     

    This is a bug reported here:

    A workaround is to:

    • create a backup of your JIRA DB and restore it into dbo schema (another DB)
    • connect Crowd to this new DB during the import
  3. I worked around this by changing the default schema of the login account JIRA uses to connect to the database. See also:

    Can't Import Users From JIRA Using SQL Server Database

  4. It is recommended that you import your JIRA users into an Internal Directory that has its 'Password Encryption' set to 'ATLASSIAN-SHA1'. Otherwise, users' passwords will not be copied across to Crowd.

    Hi, can you update this to option ATLASSIAN-SECURITY instead, to prevent misunderstandings?

    Thanks,
    Christoffer

    1. Thanks for the heads up; I've updated the page.

  5. If Postgresql is Atlassian's favourite, then why is MySQL the default?