search

nodeSolidServer / node-solid-server

Solid server on top of the file-system in NodeJS
https://solidproject.org/for-developers/pod-server
Other
1.78k stars 303 forks source link

Can't create Dokieli document in POD #1169

Open pmcb55 opened 5 years ago

pmcb55 commented 5 years ago

Trying to create a new Dokieli document in the Team inrupt April folder (https://team.inrupt.net//2019/04/PatDokieliTest) while logged into my inrupt POD with WebID (https://pmcb55.inrupt.net/profile/card#me), but I'm getting a 'Not Authorized' error. (I tried with 'https://team.inrupt.net//2019/04/PatDokieliTest' and 'https://team.inrupt.net/2019/04/PatDokieliTest').

See screenshot: DokieliNotAuthorizedError

To reproduce, just go to https://dokie.li/, login with your WebID, click the dokieli menu button and select New. Then enter 'https://team.inrupt.net//2019/04/JustinDokieliTest'.

Kevin Howard I tried creating a Dokieli doc in https://team.inrupt.net/2019/04 (where I create all of the Standup notes without issue) and I got the unauthorized error. I can’t even open a Dokieli document (https://team.inrupt.net/2019/KevinHoward) that I created directly via Data Browser. However, I can open that document using Dokieli in the Data Browser but then I get an error “Unable to fetch https://team.inrupt.net//2019/KevinHoward/index.html”

csarven commented 5 years ago

Short answer: there is no technical issue in node-solid-server or dokieli that I'm aware of, but that the dokieli UI is confusing and leading to this error.

Edit: To expand on the "no technical issue" - obviously there is - the issue occurs when there is a mismatch between the server using WebID-OIDC auth and dokieli acting like it is WebID-TLS.

Unless you want to take the WebID-TLS route, use the "OpenID Connect" button at "Sign In" which leads to using WebID-OIDC route (based on solid-auth-client). Related https://github.com/linkeddata/dokieli/issues/254 , https://github.com/linkeddata/dokieli/issues/274 .

If you feel that this addresses the issue you are experiencing, feel free to close this issue.

Aside: What needs to happen in dokieli is a revisit to the UI so that it covers both -TLS and -OIDC through for example a single input for WebID. This was actually the case prior to -OIDC, but was only intended to fetch the WebID Profile. Actual authentication happened when the server really required it (eg. at save, save as). So, we need to use the earlier UI to handle both auth mechanisms if possible.

pmcb55 commented 5 years ago

Ah ha!

The actual problem in my case I think was that I was already logged into my POD, so when I simply browsed to 'https://dokie.li/' it automatically picked up that I was logged in (which I was impressed with :) !), but it didn't realise that I'd logged in via OIDC, meaning the 'New' operation failed 'cos Dokieli attempted that operation expecting WedID-TLS.

I only realised this when I couldn't understand what you meant above when you said '...use the "OpenID Connect" button', as I didn't use the 'Sign In' dialog in the first place!

I guess we should close this issue (as it's not directly related to node-solid-server), but first, do you think it appropriate to simply extend the error message from the screenshot above to be "Could not create new document: you are not authorized. (Possibly due to this issue: https://github.com/linkeddata/dokieli/issues/274)" ?

(Just 'cos it seems like a trivial string literal update to the code, and it's only until someone actually gets to fix the UI issue, and in the meantime it could save a lot of potential frustration from the people I've told to look to Dokieli as a good example of DApps :) !)