support for local stored JWK files added #41
Merged
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 PR introduces a
FileKeyCacher
initialized at startup time. The content is generated by reading a local file (passed asLocalPath
).The file referenced by
LocalPath
can contain a plain JWK file (security alert) or an encrypted version of the plain JWK file.In the second scenario, these two config properties are required:
CipherKey
andSecretURL
.The
CipherKey
is the encoded version of the actual cypher key and requires a gocloud.dev url for the secrets package (SecretURL
)extra_config ex:
this config will use the key
smGbjm71Nxd1Ig5FS0wj9SlbzAIrnolCz9bQQ6uAhl4=
for decrypting decypher_key
and then. decrypting the content of the file./jwt.txt
Check the test in order to know how to generate such encrypted payloads
Supported providers: