[Question] How to access the created popup.html
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, nodejs
- Domain
- documentation
Research direction
Start by comparing the created popup.html and popup.html.acl with common/popup.html, then read the solid-auth-client setup referenced in the issue. Document how public access should be configured, why common/popup.html behaves differently, and whether an unminified version exists.
Written by the indexing model from the issue text.
Description
Hey Guys
Recently i tried to access my popup.html (located in the root of the server) with:
solid.auth.popupLogin({ popupUri: 'https://localhost:8443/popup.html' }) from my app.
But now i get an error which says:
The resource you are trying to access (https://localhost:8443/popup.html) requires you to log in.
And when im logged in:
You are currently logged in as https://adminjerome.localhost:8443/profile/card#me, but do not have permission to access https://localhost:8443/popup.html
I also create an popup.html.acl file in the directory with the following lines:
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
<#public>
a acl:Authorization;
acl:agentClass foaf:Agent; # everyone
acl:mode acl:Read; # has Read-only access
acl:accessTo <https://localhost:8443/popup.html>. # to the public profile
Informations:
- Startet the server with
/usr/local/lib/node_modules/solid-server/bin/solid-test start - Created the File like they said in https://github.com/solid/solid-auth-client
Now my Question:
- How can i give public access to that created
popup.html - Why does the "normal" popup.html located in:
common/popup.htmldon't need an .acl file? - Bonus: Is there an unminified-popup.html ?
Greetings
Jerome
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
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.
More from nodeSolidServer/node-solid-server
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nodeSolidServer/node-solid-server#1848 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1841 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1147 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodeSolidServer/node-solid-server#1867 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
nodeSolidServer/node-solid-server#1853 ·
All issues in nodeSolidServer/node-solid-server
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100