ARC-0080: JSON Web Tokens (JWT) Using An Algorand Account #293
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
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.
Summary
JSON Web Tokens (JWTs) are a popular and well-used format to represent a claim between two parties. They use cryptographic signatures to verify these claims and, thanks to RFC 8037, JWTs support the Ed25519 signature: the cryptographic algorithm of the private keys of Algorand accounts. Therefore, JWTs are well-suited and a viable way to be used for authentication within the context of an Algorand account.
The purpose of this proposal is to highlight how to construct a JWT with an Ed25519 public/private key pair using already well-established standards. This proposal also makes some suggestions as to the structure of the claims within the context of a an Algorand account.