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
1- When I try to upload to my web3.storage space using a different email address than my account's email as a test (in a node.js application using the w3up-client login method and then through uploadCar), I get in my application the error "Agent has no proofs for did:key:..." and I am properly not able to upload data using it, since I gave it no delegation.
2- However also, if I then use my account's email, verify it, upload data, and then try again to use the other email as a login email, the data upload is successful.
I was able to get this result (in point 1-) after I deleted the access file in .config/w3access which was created after the first login using my account's email. Otherwise (before the deletion), I was able to access my account's space and upload data by using a different email than my account's email. Is that just because I am on the same device and the same access data is being used I guess? Is that the proper and expected behavior? In that case 2 users that use the same device would be able to directly access the same space without explicit delegations? or is there more to it to be done delegation-wise that I am just not aware of? Is this the expected use of "login" to just grant access to a device/agent? Thanks for clearing any misunderstanding.
The text was updated successfully, but these errors were encountered:
1- When I try to upload to my web3.storage space using a different email address than my account's email as a test (in a node.js application using the
w3up-client
login method and then through uploadCar), I get in my application the error "Agent has no proofs for did:key:..." and I am properly not able to upload data using it, since I gave it no delegation.2- However also, if I then use my account's email, verify it, upload data, and then try again to use the other email as a login email, the data upload is successful.
The text was updated successfully, but these errors were encountered: