-
Notifications
You must be signed in to change notification settings - Fork 20
Sync should happen in core #156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Core now takes care of this, after check password the accounts is upserted |
|
Since we already retrieved the user from LDAP when core does the sync it can use the cached UserEntry |
|
Note: this would target >10.0.8 |
Codecov Report
@@ Coverage Diff @@
## master #156 +/- ##
============================================
+ Coverage 34.61% 34.88% +0.27%
+ Complexity 1375 1358 -17
============================================
Files 32 32
Lines 3975 3927 -48
============================================
- Hits 1376 1370 -6
+ Misses 2599 2557 -42
Continue to review full report at Codecov.
|
|
Should this kill setupAccount as well? |
|
@tomneedham setupAccount is code in core |
|
This needs to target the version that https://github.com/owncloud/core/pull/30638/commits is released in (10.0.8) |
aecdc1b to
ea1a442
Compare
|
faling stable10 tests until owncloud/core#30638 is merged |
|
@ownclouders rebase please |
|
Well, I rebased it |
|
Just testing this with current stable10 HEAD @ d0ee6a6a403e98a106a61b8f7dfcd06313e0b36c |
|
during testing I was worried that we removed the updateGroups call ... turns out the cache for getMemberOf is never read anyway. also, the group backend queries memberof itself and resolves nested groups. Tracking caching of groups and primarygroupid in #226 |
|
also found owncloud-archive/user_management#19 during testing group membership stuff |
No description provided.