nextcloud / nextcloud/user_saml
merge users (same sAMAccountName) - ldap / keycloak
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Steps to reproduce
- Use KeyCloak for auth
- Trying login via Kerberos
- Get another user
Expected behaviour
Although this is a different authorization method, the user must be defined as existing.
Actual behaviour
New user created with the same username and full name
Server configuration
Operating system: RHEL
Web server: Apache
Database: MySQL
PHP version: 8
Nextcloud version: (see Nextcloud admin page) 23.0
for example pin message:
How to enable or define the user mapping feature.
The same samaccountname are defined as different users. We want to map already existing users to those who log in using kerberos authorization.
We tried using social-login and OpenID Connect user backend and preferred_username.
Thanks for any help!
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
Start by reproducing the issue using Keycloak or Kerberos authentication with the listed Nextcloud 23, RHEL, Apache, MySQL, and PHP 8 configuration. Trace the user authentication and mapping flow to determine how an existing username is matched; done means the alternate authorization method maps to the existing user instead of creating a duplicate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100