Skip to content
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.

Sign up for GitHub

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

Jump to bottom

LDAP: use NC User instance to store displayname etc. #5212

Closed
blizzz opened this issue Jun 1, 2017 · 2 comments
Closed

LDAP: use NC User instance to store displayname etc. #5212

blizzz opened this issue Jun 1, 2017 · 2 comments
Assignees
@blizzz
Labels
bug feature: ldap
Milestone
Nextcloud 15

Comments

@blizzz
Copy link
Member

blizzz commented Jun 1, 2017

Otherwise, CardDAV thing is not being updated. affected down to 11.

Needs moving away from user_ldap entries in preference (→ some cleaning up) for this features
@blizzz blizzz added this to the Nextcloud 13 milestone Jun 1, 2017
@blizzz blizzz self-assigned this Jun 1, 2017
@nextcloud-bot nextcloud-bot added the stale Ticket or PR with no recent activity label Jun 20, 2018
@MorrisJobke MorrisJobke modified the milestones: Nextcloud 14, Nextcloud 15 Jul 3, 2018
@blizzz
Copy link
Member Author

blizzz commented Oct 25, 2018 •
edited
Loading

  • for quota we do this already
  • for displayname this would be delegated back to the backend → pointless. However, this is where the change-hook is emitted, too.
  • for email we do this already

so essentially, it is the one adjustment. which should also update the system addressbook.

@nextcloud-bot nextcloud-bot removed the stale Ticket or PR with no recent activity label Oct 25, 2018
blizzz added a commit that referenced this issue Oct 25, 2018
@blizzz
only write when the displayname differs, but then announce it
bbe4410 
refs #5212 and fixes #9112

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzz blizzz mentioned this issue Oct 25, 2018
Merged
@blizzz
Copy link
Member Author

blizzz commented Oct 30, 2018

Last bit done in #12054

@blizzz blizzz closed this as completed Oct 30, 2018
blizzz added a commit that referenced this issue Oct 30, 2018
@blizzz
Backport of #12054 to stable14
bdb8e37 
only write when the displayname differs, but then announce it

refs #5212 and fixes #9112

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>

do not run into UniqueConstraintViolationException

… when an unmapped user logs in for the first time when background job
mode is ajax and no memcache was configured.

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
blizzz added a commit that referenced this issue Oct 30, 2018
@blizzz
Backport of #12054 to stable13
908e6be 
only write when the displayname differs, but then announce it

refs #5212 and fixes #9112

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>

do not run into UniqueConstraintViolationException

… when an unmapped user logs in for the first time when background job
mode is ajax and no memcache was configured.

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@nextcloud-bot nextcloud-bot mentioned this issue Oct 30, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@blizzz blizzz

Labels
bug feature: ldap
Projects
None yet
Milestone
Nextcloud 15
Development

No branches or pull requests
3 participants
@MorrisJobke @blizzz @nextcloud-bot