Add an option to read SSO client secret from a file#256
Merged
Conversation
VlaDexa
force-pushed
the
client_secret_file
branch
3 times, most recently
from
fbc60f4 to
be96875
Compare
Member
|
The typos CI lint seems to be a new and unrelated issue to your PR. I think I'm going to push a commit to main fixing it so further contributions aren't confusing. Thank you for this though. |
VlaDexa
force-pushed
the
client_secret_file
branch
from
be96875 to
fc104d0
Compare
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
3 participants
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.
Issue raised in the support room. For NixOS users who don't want their secret be publicly readable.