feat(admin): support forward-auth remote user headers #25
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 #24
This adds a new setting for a remote user header. When this is set, the header with that name is read as the authenticated user's email address.
This is meant to be used with traefik's forwardAuth or oauth2-proxy. When this is enabled, end users must not have access to the admin interface directly for security reasons, but how to prevent that kind of access is outside the scope of this PR.
This works in a similar way to the GitHub authentication mechanism for creating a new user if they are the first user and no other user exists.