solid-contrib / web-access-control-tests

Tests if a Solid server implements web access control correctly
MIT License
2 stars 5 forks source link

[WiP] Investigating how to run WAC tests against CSS #27

Closed michielbdejong closed 3 years ago

michielbdejong commented 3 years ago

See also https://github.com/solid/identity-token-verifier/issues/1. Released solid-auth-fetcher@1.4.0 which contains this patch: https://github.com/solid/solid-auth-fetcher/commit/9bde828e076946fa5b8f3faa883f473ebff7c297

michielbdejong commented 3 years ago

Now at:

400 BadRequestHttpError: Error verifying WebID via DPoP-bound access token: Expected [object Set], got:
      RSA
          at DPoPWebIdExtractor.handle (/Users/michiel/gh/solid/community-server/dist/authentication/DPoPWebIdExtractor.js:50:19)
          at processTicksAndRejections (internal/process/task_queues.js:97:5)
michielbdejong commented 3 years ago

There's a puzzling situation where CSS seems to parse only the first block of: When I upload the following ACL doc:

      @prefix acl: <http://www.w3.org/ns/auth/acl#>.
      <#bobAccessTo> a acl:Authorization;
        acl:agent <https://solid-crud-tests-example-2.solidcommunity.net/profile/card#me>;
        acl:accessTo <http://localhost:3000/web-access-control-tests-1613394998650/4/accessToAndDefaultWrite/>;
        acl:mode acl:Write.

Then CSS doesn't ingest any quads. I'm not sure what's wrong with that turtle content.

michielbdejong commented 3 years ago

CSS doesn't ingest any quads

Ah I found out what's going on, I think. It only ingests relevant quads. Irrelevant ones are not ingested.