[PR #907] [MERGED] Add user_id for nextcloud example #1010

New issue

Closed

opened 2026-02-27 09:10:35 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 09:10:35 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/lldap/lldap/pull/907
Author: @ibizaman
Created: 5/2/2024
Status: ✅ Merged
Merged: 5/2/2024
Merged by: @nitnelave

Base: main ← Head: nextcloud_user_id

📝 Commits (1)

91d2994 add user_id for nextcloud example

📊 Changes

1 file changed (+5 additions, -0 deletions)

View changed files

📝 example_configs/nextcloud.md (+5 -0)

📄 Description

Context for why I believe this is a good idea:

When logging with a new user "ibizaman" through the database backend, the ID used by Nextcloud is ibizaman.
Through the LDAP backend, Nextcloud chooses the UUID field.
Through the SSO backend, integrated with LDAP, Nextcloud chooses ibizaman.

I noticed this issue while migrating users from database backend, to LDAP backend, to SSO backend where the ID was inconsistent. Also, it means that if a user was created through LDAP and tries to login through SSO, a new user will be created!

This inconsistency makes no sense IMO. By overriding the UUID field to be the user_id field, the ID assigned to a new user is consistent whatever the backend used.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/lldap/lldap/pull/907 **Author:** [@ibizaman](https://github.com/ibizaman) **Created:** 5/2/2024 **Status:** ✅ Merged **Merged:** 5/2/2024 **Merged by:** [@nitnelave](https://github.com/nitnelave) **Base:** `main` ← **Head:** `nextcloud_user_id` --- ### 📝 Commits (1) - [`91d2994`](https://github.com/lldap/lldap/commit/91d2994b886e86ca5aa677ab91a06a2382dcfdea) add user_id for nextcloud example ### 📊 Changes **1 file changed** (+5 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `example_configs/nextcloud.md` (+5 -0) </details> ### 📄 Description Context for why I believe this is a good idea: - When logging with a new user "ibizaman" through the database backend, the ID used by Nextcloud is `ibizaman`. - Through the LDAP backend, Nextcloud chooses the `UUID` field. - Through the SSO backend, integrated with LDAP, Nextcloud chooses `ibizaman`. I noticed this issue while migrating users from database backend, to LDAP backend, to SSO backend where the ID was inconsistent. Also, it means that if a user was created through LDAP and tries to login through SSO, a new user will be created! This inconsistency makes no sense IMO. By overriding the `UUID` field to be the `user_id` field, the ID assigned to a new user is consistent whatever the backend used. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>