#433 closed task (fixed)
Migrate Users/Logins
Reported by: | landauf | Owned by: | admin |
---|---|---|---|
Priority: | major | Milestone: | IT: Server Migration |
Component: | IT | Version: | |
Keywords: | Cc: | ||
Referenced By: | References: |
Description (last modified by landauf)
Users from the old system should be migrated to the new server. We don't necessarily need to migrate ALL users if it causes too much work because a lot of users are inactive for years.
If possible, the credentials for login should remain the same.
The roles for each user will be defined manually.
Change History (4)
comment:1 Changed 9 years ago by landauf
- Description modified (diff)
comment:2 Changed 8 years ago by lferran
- Users in the old server are defined under /var/svn/svnusers. Most of them can potentially be omitted for the migration, since they are inactive since long time ago.
- Only the MD5 hash of the passwords are stored in the old server.
- Possible users migration procedure:
- Select which users should be migrated
- For each selected user:
- Go to the ldap admin panel and copy one of the existing users.
- Change credentials with the credentials of the user that is being migrated
- In the password field add a random-generated password, that will be sent to the user. Additionally, we will ask the user to log in into roundcube and change its own password.
- If the user to migrate has login access to the server:
- Copy user's ssh public key from the old server to the new one
- Copy the user's shadow entry too, so that the user can maintain its unix password.
comment:3 Changed 8 years ago by lferran
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 8 years ago by lferran
UNIX users selected in ticket:27 have been created in the new server:
- Login passwords have been kept
- ssh authorized keys have been copied
- Preferred shell has been migrated too
- Sudoer permissions have been kept too!
Note: See
TracTickets for help on using
tickets.