Description
Describe your use-case which is not covered by existing documentation.
-
In access-control.adoc, replace:
Examples include enabling account signup for Jenkins user database, or various other authorization realms, many of which (GitHub, Google, GitLab, etc.) allow anyone to sign up for an account.with:
The default behavior enables account signup for the Jenkins user database, which is recommended for most production systems. Other authorization realms can be specified here, although note that many of these (such as GitHub, Google, GitLab) allow anyone to sign up for an account. -
In managing-security.adoc:
-
Why do we have the == header titled for a button that no longer exists? My suggestion is that we change this to be "== Configure Global Security" and use what is now the last paragraph as the lead-in to the section.
-
I would then rewrite the paragraph about "Enabling Security" a bit and put it into a Note. Begin with "Earlier releases included an Enable Security checkbox. This option is removed from Jenkins 2.214 and Jenkins LTS 2.222.1 and later releases." Then maybe discuss what unchecking this option meant, or say something like "This option can no longer be disabled. This means that only users who log in with a username and password can perform operations that are not allowed for anonymous users and logged-in users have full control to all operations. The operations available to logged-in users can be restricted through the configuration of the authorization strategy that is used."
-
Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.
This started as comments to #7166 but it belongs in its own PR.
Are you interested in contributing a fix?
I will submit a PR