New configuration to (dis-)allow external users create access tokens #21438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #21403
Add a new configuration-entry to manage creation of access-tokens for external users.
Description
The configuration's value is considered when a user wants to create a new access token. For internal users, it doesn't make a difference, for external ones, it would forbid creating a token if set to
false
. Otherwise, external users are also allowed to create access tokens.Starting with graylog 6.2, the configuration is set to not allow external users creating an access token. Before that version, it is allowed, to prevent a breaking change.
Motivation and Context
How Has This Been Tested?
There are test-cases covering all three options (internal user, external with setting being
true
and external user with setting beingfalse
).Types of changes
Checklist: