feat: support forcing internal authentication for selected actions#5912
Open
midoelhawy wants to merge 1 commit into
Open
Conversation
|
Thank you I'm in the middle of trying now I'm almost there |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change adds a new configuration option,
authHTTPForceInternalUsersForActions, to allow specific actions to be authenticated usingauthInternalUserseven whenauthMethodis set tohttp.This is useful when most actions should be authenticated by an external HTTP authentication service, while a small subset (for example
publishorapi) should use the built-in user database.Example:
With this configuration:
publishandapiare authenticated usingauthInternalUsers.metricsandpprofremain excluded from HTTP authentication.