nodeSolidServer / nodeSolidServer/node-solid-server

Can't create Dokieli document in POD

Open
#1,169 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the authorization failure at dokie.li using the Team Inrupt folder and the documented WebID, then compare creating and opening the document through Dokieli and the Data Browser. Trace the server's authorization handling for these requests; done means an authorized user can create and open the Dokieli document without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.