-
Suggestion
-
Resolution: Unresolved
-
None
-
29
-
Hi everyone,
Thank you for your votes and comments on this feature request. Whilst this is something we would like to implement some day, it is not planned to be a part of a forthcoming release.
We will be focussing on improving the integration of Crowd within our Atlassian suite of products, as well as simplifying and improving the overall user management and a unified administrative experience.
If our release plan changes and this feature request becomes a priority, this ticket will be updated. If you'd like to better understand how we make roadmap decisions, have a read of : https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy
Cheers, Helen Hung
Atlassian Product Management
I would like to move users from one directory to another one. The target scenario in our case would be creating an archive directory that contains users that are not longer required (and should not only be inactive).
- blocks
-
JRACLOUD-27868 Migrating users from one directory to another (part 2)
- Closed
-
CWD-2799 Add a move/copy user facility to the CrowdService to allow embedding products to move users between directories.
- Closed
-
CONFSERVER-25630 Make it possible to move users between directories
- Gathering Interest
-
ID-8983 Make it possible to move users between directories
- Gathering Interest
-
JRASERVER-27868 Provide the ability to migrate users from one directory to another
- Future Consideration
- is duplicated by
-
CWD-2799 Add a move/copy user facility to the CrowdService to allow embedding products to move users between directories.
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
You know, I don't see much for SQL on the documentation site, but I think the dev documentation will cover what you need: https://developer.atlassian.com/server/crowd/database-schema-and-example-sql-for-crowd/
That's what I used.
Our implementation is very simple and does not use nested groups, so all I do is get the source directory ID:
// MSSQL select * from cwd_directory
Then I grab the users, which I usually tag with a temporary group:
Then I grab the users' memberships:
Then I use these files for the CSV import to the new directory.
NOTE: even though you're using delegated LDAP, you'll still need to have a password column. Doesn't matter what text you put in there, as Crowd will execute an AD lookup at the moment of logon and update this value as expected, so it's just a placeholder.
Once the users have synced down to the client apps, then I delete them from the source directory and send out the 'migration complete' mail.
So far for us, this has all been very safe and easy to do.