-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dpop payload claim invalid value #1247
Comments
Hi @sadukar , thank you very much for this issue. Which OIDC server are you using? I'am looking at one to test this killer feature properly. |
Hi thanks for the quick reply. Other than the claim name it seems to be working ok the jwt is created and signed properly, will need to test the refresh token behavior and compatibility with reference tokens but it looks very promising, thanks for all the hard work. |
hi @sadukar , I fixed it in the latest version. |
@sadukar , I'am waiting for your feedback if It require another fix ! |
Thank you so much, will follow up after testing |
Did you succed @sadukar ? |
Hi @sadukar , did you succed to use it? |
Hi @sadukar we fixed everything with DPOp use. Do you still have some problem with it? |
hi @sadukar , did it works? |
hi @sadukar , I close the issue. It work well on my side. Feel free to reopen it if you need it. |
Issue and Steps to Reproduce
It seems like there is a typo in the jwt.ts file where setting the claim
`export const generateJwtDemonstratingProofOfPossessionAsync = (jwk, method = 'POST', url: string, extrasClaims={}) => {
}`
According to spec the claim jit does not exist but it should be jti, this results in invalid jti claim result on all dpop enabled requests
Versions
Screenshots
Expected
Actual
Additional Details
The text was updated successfully, but these errors were encountered: