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
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
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
Cecylia Bocovich
Wiki Replica
Commits
6166826e
Commit
6166826e
authored
4 years ago
by
Peter Palfrader
Browse files
Options
Downloads
Patches
Plain Diff
A word more on updating keys, and a cross-reference in a good place
parent
cbf01422
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/accounts.md
+4
-0
4 additions, 0 deletions
doc/accounts.md
howto/create-a-new-user.md
+3
-0
3 additions, 0 deletions
howto/create-a-new-user.md
with
7 additions
and
0 deletions
doc/accounts.md
+
4
−
0
View file @
6166826e
...
...
@@ -295,3 +295,7 @@ ticket for you. The sponsor should [create a new ticket in GitLab](https://gitla
least one Tor person other than your sponsor.
*
The ticket should be OpenPGP signed with the current valid OpenPGP key of
your sponsor.
### Actually updating the keyring ###
See the
[
new-user HOWTO
](
../howto/create-a-new-user.md
)
.
This diff is collapsed.
Click to expand it.
howto/create-a-new-user.md
+
3
−
0
View file @
6166826e
...
...
@@ -238,3 +238,6 @@ group of machines, as the `mirroradm` user:
The account-keyring repository contains an update script
`./UPDATE`
which takes
the ldap username as argument and automatically updates the key.
If you /change/ a user's key (to a new primary key), you also need to update
the user's
``keyFingerPrint``
attribute in LDAP.
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