Federated User with port# at the end of the address does not work with circles
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 177
- Forks
- 68
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 60
Description
Dear All,
im running a NextcloudPi behind a Fritzbox. In order to have it accessible from the Internet portmapping is enabled.
I can add a federated user like <user@xxxx.myfritz.net:#portnumer> for sharing within a hosted nextcloud instance and do have access to the shared objects within the PI nextcloud instance behind the fritzbox. So thats fine.
Next step is to create circles. Adding a user in the form of <user@xxxx.myfritz.net:#portnumer> is not supported by the circles app.
However, without the portnumber the user cannot be found (obviously).
Is this a known problem? Any workaround you would suggest?
Brgds DerBusIsVoll
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
The issue reports that Circles rejects federated users written with a port number, while ordinary federated sharing accepts them. No source file, test, reproduction steps, or entry point is named; start by reproducing the user lookup in the Circles app and compare it with the working federated-sharing path. Done means a federated user with a port can be added to a circle and access shared objects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100