Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do I migrate the LDAP authentication user directories, users, groups and group memberships to Crowd.

I am using JIRA 5.1.5

JIRA is configured with:

· External user management off

· 3 User Directories

o 2 configure internal with LDAP authentication user directory UD1 and UD2

o 1 JIRA Internal Directory.

I would like to migrate to Crowd 2.6.0, How do I migrate the LDAP authentication user directories, users, groups and group memberships to Crowd.

This is what I tried:

I created a Delegated Authentication (named ITDA) with synchronization disabled and all permissions enabled.

I tried importing the JIRA users into Crowd Directory ITDA using the Atlassian Importer, but it does not import all the users and their group membership. It seem to import the users that do not exist in the ITDA LDAP tree. Is this the correct response.

I configured JIRA to use the Crowd User Directory (read/write) and I disabled UD1 and UD2. When I disabled UD1 and UD2 most of the users are missing from the user browser.

What am I doing wrong.

1 answer

1 accepted

0 votes
Answer accepted

Hi Jerome,

Regaridng your import issue, by default Crowd will double check if the user exist on the configured LDAP server which configured with ITDA. If the user is not searchable on your LDAP server, Crowd will not migrate it. Hence Crowd suppose to exclude all users that is not exist in the ITDA LDAP tree and migrated all that exist in the ITDA LDAP tree.

Regarding your second query, it is expected behavior for JIRA to not included all the users that no longer registered on your JIRA server in the user browser.

Hope it helps.

Septa Cahyadiputra

I notice the following exceptions in the crowd log files when I attempt to import users from JIRA.

2013-03-19 07:40:27,796 http-8095-1 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 0, SQLState: null
2013-03-19 07:40:27,796 http-8095-1 ERROR [org.hibernate.util.JDBCExceptionReporter] failed batch
2013-03-19 07:40:27,796 http-8095-1 ERROR [hibernate.event.def.AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(

2013-03-19 07:40:27,798 http-8095-1 ERROR [persistence.hibernate.batch.AbstractBatchProcessor] Could not process class com.atlassian.crowd.model.membership.InternalMembership: com.atlassian.crowd.model.membership.InternalMembership@3a67ba87[parentId=133164,childId=71402,membershipType=GROUP_USER,groupType=GROUP,parentName=OM_group,lowerParentName=om_group,childName=gn803f,lowerChildName=gn803f,directoryId=32772]
org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update

Also what is the procedure to migrate user autenication to Crowd base on this cionfiruration of JIRA.

Judging from your stack trace, there might be a duplicate on your JIRA database that Crowd does not accept during the migration process.

In regards to your second query, please refer to our documentation here. Since you have multiple directory on JIRA side, you might want to consider using CSV import and create each three directory on Crowd so you could mimic the user management state as similar as possible with the previous state.

However, please note that CSV import require manual work to compose a valid and good CSV files.

Hope it helps.

Septa Cahyadiputra

In the CVS file is the password a direct feed from the database table cwd_user.credential

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events