nextcloud / nextcloud/user_saml
Problem with user authorization by CAS - ObjectGUID attribute
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 104
- Forks
- 85
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 16
Description
Nextcloud version: 25.0.7
Hello,
We have a nextcloud service in our company with the "LDAP user and group backend" plugin installed, which had default settings when the service was launched. People who logged in to the service have a username after the ObjectGUID attribute.
The problem appeared when authorization was started by CAS using the "SSO & SAML authentication" plug-in. The plugin does not use the ObjectGUID attribute for UID mapping.
Is there any possibility to run authorization after CAS using the ObjectGUID attribute? Maybe there is some tool to migrate from ObjectGUID to e.g. User Principal Name (UPN)?
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 reviewing the LDAP user and group backend's ObjectGUID UID mapping alongside the SSO & SAML authentication plugin's CAS UID mapping. Determine whether existing users can be matched or migrated to UPN-based identifiers; done means CAS authentication resolves to the existing Nextcloud accounts without duplicate users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100