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 ath
claim check
#151
Comments
What is the difference you identified? I had not spotted any issues. |
We mainly ran into this one (@ylebre told me):
|
We updated to require the presence of the ath claim in the dpop proof, after which the tests started failing. it seems that the solid-auth-fetcher code does not add the ath claim to the proof, which was valid for dpop 01 but no longer the case with 04 and 11. |
Ah ok sorry, I missed this point in 04:
So it was already required in 0.9.0. I'll fix it! |
ath
claim check
I'm working on the following labelling of spec versions:
This ticket is for switching from solid-auth-fetcher to a new client lib that send the right |
As described in #150, there is a new version of the DPoP spec, so we need to update how our test suites make requests to storage servers.
In the jest-based tests (solid-crud-tests, web-access-control-tests, webid-provider-tests) this probably means we'll have to switch away from solid-auth-fetcher. I'll try to find time to look into that.
@edwardsph which version of the DPoP spec does the harness follow, and/or is that configurable?
The text was updated successfully, but these errors were encountered: