nextcloud / nextcloud/lookup-server
Reject duplicate users in a Global Scale deployment
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 25
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
In a Global Scale deployment, duplicate users should be rejected.
For example if we have two nodes gs-node01 and gs-node02, we shouldn't make it possible to have
user1@gs-node01
user1@gs-node02
in the users table as this situation leads to inconsistent behavior: to which node is the user redirected when he/she logs into the instance through the Global Site Selector Node?
The fact that is a Global Scale deployment can be based on the GLOBAL_SCALE boolean flag.
Note that this check should be done before creating the user locally in the Global Scale Node to avoid creating another inconsistent situation in which the user is created in the Global Scale Node but not in the Lookup Server. See this issue as an example of this scenario.
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
Trace the user-creation path and the users table, using the GLOBAL_SCALE flag to identify the Global Scale behavior. Check how the Lookup Server is contacted before local creation and define completion as duplicate users being rejected without leaving a local-only user behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100