Use AUTH-SOURCE to retrieve encrypted token #25
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
Instead of storing the token along with the rest of the users customization, use the auth-source library so we can store the token in an encrypted file instead. Don't require CL-LIB anymore as we no longer need CL-ASSERT.
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.
Instead of storing the token along with the rest of the users
customization, use the auth-source library so we can store the token in
an encrypted file instead.
Don't require CL-LIB anymore as we no longer need CL-ASSERT.
This is a backwards incompatible change as I prefer to not enable users to storing sensitive information in plain text, but could leave pivotal-token as customizable variable so the change is backwards compatible if you prefer.