KeyProvider-style API for signature schemes (HMAC)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- authentication
Research direction
Start with the KeyProvider API and HMACAlgorithm, then review README, EXAMPLES.md, and the API documentation to compare the existing asymmetric flow with HMAC. Define the proposed symmetric-key provider behavior, including key IDs and claims validation, and document how the API would support key rotation before implementation.
Written by the indexing model from the issue text.
Description
Checklist
- I have looked into the Readme and Examples, and have not found a suitable solution or answer.
- I have looked into the API documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Describe the problem you'd like to have solved
I am working on a project just for fun to learn a little more about JWTs
There is a handy KeyProvider API for asymmetric encryption schemes that allow identifying keys by a KID and validating a claims from a set of potential keys. A similar API for HMAC (which has no public key) is not available.
KeyIDs are handy when setting up secret key rotation, so an equivalent API for HMAC would be handy.
Describe the ideal solution
A KeyProvider-style API specifically for HMAC which does away with the public key part aspect and solely focuses on keys with only a private portion (could also cover symmetric keys).
Alternatives and current workarounds
I considered extending HMACAlgorithm to do this, but all the relevant classes are locked down.
Additional context
None
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 945
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from auth0/java-jwt
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 72/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
checkstyle/test-configs#263 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
[BUG]茶杯方块在取茶时会引发崩溃 Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
1.0.0-alpha2 Type/Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wso2/dpdp-accelerator#272 ·