CAS and LDAP backend not working together anymore
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 17
- Forks
- 19
- Avg merge
- 11h 40m
- Merged PRs (30d)
- 2
Description
Hi,
Since the beginning of the year the CAS and LDAP backend not working together anymore.
In the database when OCA\UserCAS\User\Backend is set for a user only CAS working not the client or Owncloud form. When OCA\User_LDAP\User_Proxy is set only client or Owncloud form working.
We don't know where is the problem, we have this error on the log :
User already provided by another backend(OCA\User_LDAP\User_Proxy !== OCA\UserCAS\User\Backend), skipping."}
Returned account has different backend to the requested backend for sync
Thank you for your 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
No files or tests are named. Start by reproducing the issue with OCA\UserCAS\User\Backend and OCA\User_LDAP\User_Proxy configured for the same user, then trace the backend-selection and sync log messages. Done means CAS and LDAP-backed authentication paths work together without the backend-mismatch errors.
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
- 30/100