use JWT_PUBLIC_KEY from environment rather than file #2865
Merged
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
Signed-off-by: John DeAngelis <[email protected]>
johndeange
requested review from
rajohnson90,
fpigeonjr,
devops-chris,
maiyerlee and
Santi-3rd
maiyerlee
approved these changes
Sep 30, 2024
fpigeonjr
approved these changes
Sep 30, 2024
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.
What changed
The higher environments in Azure will use a different Public/Private Key pair.
This PR prepares for the functionality to allow different keys by deleting the Public Crypto Key in the repo and using environment variable instead.
Issue
#2811
How to test
Automated tests pass.
Definition of Done Checklist
Links
If relevant, e.g. for a link to a piece of markdown documentation