Implemented: Remove demo secret keys from security.property and add a gradle task to generate and set the keys#969
Open
jacopoc wants to merge 2 commits intoapache:trunkfrom
Open
Implemented: Remove demo secret keys from security.property and add a gradle task to generate and set the keys#969jacopoc wants to merge 2 commits intoapache:trunkfrom
jacopoc wants to merge 2 commits intoapache:trunkfrom
Conversation
… gradle task, generateSecretKeys, to generate and set the keys The new task is automatically triggered when the loadAll is executed.
… 'processResources' runs after it
|
Contributor
|
Hi @jacopoc, I vaguely remember I suggested some years ago to use a secret key generator rather than stocking it in a properties file. |
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.



The new task, generateSecretKeys, is automatically triggered when the loadAll is executed.