You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both resource servers and clients needs to hash bound authorization tokens during a normal DPoP authorization flow. If done incorrectly on either side it will result in a ath mismatch.
A clear and concise description of what you want to happen.
It would be helpful if the dpop-package had a utility function to hash a token according to the specification. Then both clients and resource servers could be confident in that the hash is made according to specification and reduce likelihood that a ath mismatch will occur.
Additional Notes
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Contact Details
[email protected]
Is your feature request related to a problem?
Both resource servers and clients needs to hash bound authorization tokens during a normal DPoP authorization flow. If done incorrectly on either side it will result in a
ath
mismatch.A clear and concise description of what you want to happen.
It would be helpful if the dpop-package had a utility function to hash a token according to the specification. Then both clients and resource servers could be confident in that the hash is made according to specification and reduce likelihood that a
ath
mismatch will occur.Additional Notes
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: