Skip to content

LDAP: determine shares of offline users only when needed - #27698

Merged
blizzz merged 1 commit into
masterfrom
fix/25761/userexistsonldap-loop
Jun 28, 2021
Merged

LDAP: determine shares of offline users only when needed#27698
blizzz merged 1 commit into
masterfrom
fix/25761/userexistsonldap-loop

Conversation

@blizzz

@blizzzblizzz commented Jun 28, 2021

Copy link
Copy Markdown
Member

The story behind is this:

  1. On a migration call that loops over all users
  2. Also all known LDAP users get into consideration
  3. including those that are not found on LDAP anymore (OfflineUser)
  4. and userExists is run against each user
  5. which also causes an existency check against the LDAP server
  6. for which the DN is required
  7. the getter of the OfflinerUser triggered fetching all details
  8. including checking whether they are a sharee
  9. which depending on the share provider logic might invoke a user existence check

But the only place where we need the information is the ldap:show-remnants command.

fixes a segfault on a migration step of accessibility app on upgrade #25761 (wrong issue)

- determine shares may via Sharing code result in user exists checks
- this may result in an infinite loop when user exists was called before
- the info is really only required at one occ command
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzz

Copy link
Copy Markdown
MemberAuthor

/backport to stable22

@blizzz

Copy link
Copy Markdown
MemberAuthor

/backport to stable21

@artongeartonge left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM :)

@Pytal

Copy link
Copy Markdown
Member

Drone 🤷‍♂️

@blizzz

Copy link
Copy Markdown
MemberAuthor

Drone man_shrugging

unrelated

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@blizzz@Pytal@artonge