Skip to content

Conversation

@blizzz
Copy link
Member

@blizzz blizzz commented Jun 28, 2021

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 <[email protected]>
@blizzz
Copy link
Member Author

blizzz commented Jun 28, 2021

/backport to stable22

@blizzz
Copy link
Member Author

blizzz commented Jun 28, 2021

/backport to stable21

Copy link
Contributor

@artonge artonge left a comment

Choose a reason for hiding this comment

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

LGTM :)

@Pytal
Copy link
Member

Pytal commented Jun 28, 2021

Drone 🤷‍♂️

@blizzz
Copy link
Member Author

blizzz commented Jun 28, 2021

Drone man_shrugging

unrelated

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants