Using solid-node-client with an index.html in pod root
Login and go to https://jeff-zucker.solidcommunity.net:8443/
Attempt to use @inrupt/generate-oidc-token to get a token to use OIDC rather than username/password fails with :
(node:2152992) UnhandledPromiseRejectionWarning: OPError: invalid_grant (Mismatching redirect uri) at processResponse (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/openid-client/lib/helpers/process_response.js:45:13) at Client.grant (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/openid-client/lib/client.js:1237:26) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Client.callback (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/openid-client/lib/client.js:460:24) at async AuthCodeRedirectHandler.handle (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/@inrupt/solid-client-authn-node/dist/login/oidc/redirectHandler/AuthCodeRedirectHandler.js:77:24) at async ClientAuthentication.handleIncomingRedirect (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/@inrupt/solid-client-authn-node/dist/ClientAuthentication.js:70:34) at async Session.handleIncomingRedirect (/home/jeff/Dropbox/Web/solid/generate-oidc-token/node_modules/@inrupt/solid-client-authn-node/dist/Session.js:45:35) at async /home/jeff/Dropbox/Web/solid/generate-oidc-token/dist/index.js:82:9 (node:2152992) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:2152992) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Seems to be a good candidate has owner. It has Read to everybody and ReadWriteControl to the owner itself.
# Root Meta resource for the user account # Used to discover the account's WebID URI, given the account URI <https://bourgeoa.solidcommunity.net:8443/profile/card#me> <http://www.w3.org/ns/solid/terms#account> </>.
Test server https://solidcommunity.net:8443 updated to latest mashlib v1.7.3
Allready tested. If no regression shall be available as NSS latest in a few days.
How was the owner tested?
Can you clarify (in the docs?) as to how NSS considers an agent to be owner? If/how can the owner be changed?
<subject> solid:account </>from
https://pod/.metacan change the owner. By default
https://pod/profile/card#meis the owner and has Write access (anybody has Read)
What does the error response look like for an owner without the required access privileges on the resource?
The owner is allways advertised in root/ representation as text-turtle and on root/.meta depending on access privileges.
There is no check to forbid DELETE root/.meta, nor that PUT checks that the triple defining the owner exist