"Strange ... not authenticated ... to read preference file"
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 5
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
"Strange - you are not authenticated (properly logged in) to read preference file." alert when looking at chat, when logged in as the owner of the pod.
Console:
(Logged in as <https://solidos.solid.community/profile/card#me> by authentication)
mashlib.min.js:17 logIn: Already logged in as <https://solidos.solid.community/profile/card#me>
/settings/prefs.ttl:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
2mashlib.min.js:17 HTTP status 401 for preference file <https://solidos.solid.community/settings/prefs.ttl>
/settings/privateTypeIndex.ttl:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)
mashlib.min.js:17 Complaint: loadPubicIndex: loading public type index Error: Fetcher: <https://solidos.solid.community/settings/privateTypeIndex.ttl> Unauthorized
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the alert in the chat view while authenticated as the pod owner, then inspect the requests for /settings/prefs.ttl and /settings/privateTypeIndex.ttl shown in the console. Trace how mashlib.min.js handles the 401 responses and verify the alert no longer appears when the owner is properly authenticated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100