nodeSolidServer / nodeSolidServer/node-solid-server
Extend 403 template to request access
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
No permission to access this resource
You are currently logged in as https://ren.solid.community/profile/card#me, but do not have permission to access https://stimpy.solid.community/inbox/.
Next step in the interaction:
Offer an input (button or whatever) to the user to make a request to access the resource.
There can be a number of ways to that.. config setting that shows the request form on all 403s and sends a notification to an (dedicated?) inbox, and/or if the resource has a dedicated inbox....
I said template in the title of this issue, but it'll act more like its own application (so that the server is not expected to process it like an HTML form) that sends a notification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the current 403 template and the authorization path that produces it. Review how the server identifies the logged-in user, target resource, and any dedicated inboxes before choosing a request flow. Done means a user without permission can submit an access request and the intended recipient receives a notification, but the payload leaves the configuration and notification design unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100