nextcloud / nextcloud/user_saml
UPN account do not match already activated Sam accounts (Azure and LDAP sync)
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Steps to reproduce
- User have already accounts via LDAP plugin
- SAML on Azure successfully enrolled
- User accounts do not match
Expected behaviour
I expect that user who have already an account match the new login method. SAM accounts match the new UPN
Actual behaviour
New user accounts are created.
Operating system: Linus 5.14
Database: mysql 10.9.3
PHP version: 8.013
Nextcloud version: 25.0
Where did you install Nextcloud from:
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 reproducing the login with an existing LDAP account and an Azure SAML UPN, then trace the SAML account-matching entry point. Done means an already activated LDAP account is reused for the matching UPN instead of creating a new account.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, php
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100