Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
5a3e0a7d
Verified
Commit
5a3e0a7d
authored
7 months ago
by
Jérôme Charaoui
Browse files
Options
Downloads
Patches
Plain Diff
draft user renaming docs (tpo/tpa/team#41681)
parent
1fd2ac2c
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#187826
passed with warnings
7 months ago
Stage: build
Stage: test
Changes
2
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
howto.md
+1
-0
1 addition, 0 deletions
howto.md
howto/rename-a-user.md
+42
-0
42 additions, 0 deletions
howto/rename-a-user.md
with
43 additions
and
0 deletions
howto.md
+
1
−
0
View file @
5a3e0a7d
...
...
@@ -31,6 +31,7 @@ various procedures not necessarily associated with a specific service.
*
[
quintex
](
howto/quintex
)
*
[
raid
](
howto/raid
)
*
[
rename-a-host
](
howto/rename-a-host
)
*
[
rename-a-user
](
howto/rename-a-user
)
*
[
retire-a-host
](
howto/retire-a-host
)
*
[
retire-a-user
](
howto/retire-a-user
)
*
[
upgrades
](
howto/upgrades
)
...
...
This diff is collapsed.
Click to expand it.
howto/rename-a-user.md
0 → 100644
+
42
−
0
View file @
5a3e0a7d
[[
_TOC_
]]
This document explains how to handle requests to rename a user account.
# Requirements
-
the new LDAP username
-
the new "full name"
-
a new or updated GPG key with the new email
-
a new mail forwarding address, if needed
# Main procedure
1.
Update
`account-keyring.git`
with the new (or updated) GPG key
2.
With
`ldapvi`
, update the user and group names in the LDAP database
(including the DN), along with the new GPG fingerprint if a new key is to be
associated with the account and forwarding address if applicable
3.
Using
`cumin`
, rename home directories on hosts
4.
Optionally, add the previous forwarding to the virtual alias map on
`eugeni`
5.
Update the information on the main website
# GitLab
GitLab users may rename their own accounts with the User Settings panel.
# Nextcloud
Changing the login name is
[
not supported
][]
at all in Nextcloud, only the
display name can be changed.
[
not supported
]:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_user/user_configuration.html#renaming-a-user
If a new account is created as part or the renaming process, it's possible to
"transfer" files and shares from one account to the other using the
[
files:transfer-ownership
][]
command via the CLI. This particular option is
however untested, and TPA doesn't have access to the hosted Nextcloud CLI.
[
files:transfer-ownership
]:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html#transfer
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment