nextcloud / nextcloud/lookup-server
Enhance the user handling logic to accept unsigned user upsert/delete operations for troubleshooting and testing
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 25
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
In the following scenarios:
- initial installation of the lookup server for a Global Scale deployment,
- debug of interactions with other components of an already existing Global Scale deployment,
- other
it makes sense to test the lookup server by calling the REST API from a command line client, such as curl.
However, it seems that it is not possible without signing the request (meaning that there should exist a Nextcloud instance with a domain matching the one specified in field federationId).
It would be good then to introduce an operating mode that doesn't check the signature, to be enabled during troubleshooting. For example a configuration switch in config.php?
Maybe @schiessle you can have a look?
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
No files or tests are named. Start by tracing the REST API handlers for user upsert and delete operations and the signature-validation and configuration code. Done means a clearly controlled troubleshooting mode permits unsigned requests for those operations without changing the normal signed-request behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100