anusii / anusii/solidui

SOLIDUI: support a user with pod and webid on different servers

Open
#383 1 comment 0 reactions 1 assignee View on GitHub

@jesscmoore is already working on this.

Since Jul 23, 2026.

Dominant language
Dart
Stars
7
Forks
2
Avg merge
1d 12h
Merged PRs (30d)
3

Description

Image

Describe the Bug

Solidui does not support a user that had a pod on server 2, which is linked to a webid on server 1. Which is the case for a user that wants multiple pods for redundancy or different purposes, but a single webid. Ideally the registration process in solidui would allow a user to optionally use an existing webid with a new pod.

Currently solidpod and solidui derive the resourceUrl (when full url not provided) from a user's webid.
After that is fixed in solidpod (issue #https://github.com/anusii/solidpod/issues/692), solidui will need updates:

  • support for pod url different to webid (scheme, domain, podname) should also be added in solidui.
  • update registration to support (an advanced option) of pod url different to webid (scheme, domain, podname)
Current errors

However, on login to pod https://pods.privateinsights.au/jessicamoore with
linked webid
https://pods.solidcommunity.au/jessicamoore/profile/card#me

I get these errors below. It seems to be assuming I am logging into my pod on solidcommunity.


flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/logs/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/data/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/encryption/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/profile/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/sharing/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/notifications/
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/sharing/public-key.ttl.acl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/logs/permissions-log.ttl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/logs/permissions-log.ttl.acl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/profile/.acl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/notifications/.acl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/shared/.acl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/encryption/ind-keys.ttl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: Failed to check resource status.
flutter: URL: https://pods.solidcommunity.au/jessicamoore/notepod/encryption/enc-keys.ttl
flutter: ERR: {"name":"UnauthorizedHttpError","message":"","statusCode":401,"errorCode":"H401","details":{}}
flutter: KeyOperations => loadEncryptionKey() error: _Exception
flutter: Exception: Failed to get resource https://pods.solidcommunity.au/jessicamoore/notepod/encryption/enc-keys.ttl

## To Reproduce

Steps to reproduce the behavior:

1. Run notepad
2. Select server 'https://pods.privateinsights.au'
3. Click 'Login' with email and password for jessicamoore on privateinsights pod
4. It shows a security key entry dialog, that should be entering it for the first time, however, instead is asking for the key I've used previously. And on entering the desired key get the above errors.


## Expected Behaviour

I can login to my pod on privateinsights.au which is linked to webid on solidcommunity.

## Screenshots

See comment

## Context

Where has the issue been observed:

- [ ] Android
- [ ] Chrome
- [ ] iOS
- [ ] Linux
- [x] macOS
- [ ] Web
- [ ] Windows

[Add any other context about the problem here.]

App Version: Testing with Notepod 1.0.14+15 
Flutter Version: Flutter 3.44.2

## Closing Criteria

Checklist for closing the issue:

- [ ] No errors from `make prep`
- [ ] All tests pass `make qtest`
- [ ] User can login to a pod which has webid on another solid server

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.