adding basic auth #223
Open
adding basic auth #223
Conversation
This file contains 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 is an extremely basic way to add basic authentication for oxidizied-web. User can set environment variables BASIC_AUTH_USERNAME and BASIC_AUTH_PASSWORD, after which all the requests to the oxidized will need to provide basic authentication. LibreNMS integration remains functional, as one can provide UN/PW in the URL.
I am aware that one can easily add reverse proxy to achieve the same functionality, but I feel that having ability to do it quickly and easily via environment variables would simplify things for those who choose to run oxidized in container environments.