[Auth] server public key as a base64 encoded string #947
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
jbygdell
force-pushed
the
feature/issue_886
branch
2 times, most recently
from
6cadf94 to
4c668b8
Compare
pahatz
approved these changes
Jul 23, 2024
jbygdell
force-pushed
the
feature/issue_886
branch
from
4c668b8 to
f91d9b5
Compare
By serving the public key as a base64 encoded string a user can actually use it by calling the info endpoint like this: `curl -sL HOSTNAME/info | jq -r '.public_key | @base64d' > pubkey.pem`
jbygdell
force-pushed
the
feature/issue_886
branch
from
f91d9b5 to
0d760ea
Compare
kostas-kou
approved these changes
Jul 25, 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.
Related issue(s) and PR(s)
This PR closes #886.
Description
Serve the public key from the info endpoint as a base64 encoded string instead of a hex string.
How to test
The file should look like this: