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.

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

Peoplepicker: search users in nested security groups #1173

Closed
RicoNL opened this issue Mar 29, 2022 · 2 comments · Fixed by #1205
Closed

Peoplepicker: search users in nested security groups #1173

RicoNL opened this issue Mar 29, 2022 · 2 comments · Fixed by #1205
Labels
status:fixed-next-drop Issue will be fixed in upcoming release.
Milestone

Comments

@RicoNL
Copy link
Contributor

RicoNL commented Mar 29, 2022

Category

[X] Enhancement

[ ] Bug

[ ] Question

Version

Please specify what version of the library you are using: [ 3.7.0 ]

Expected / Desired Behavior / Question

Make users from nested Security groups searchable when the groupId is specified in the PeoplePicker.

Changing 'members' to 'transitiveMembers' in PeopleSearchService.ts | searchTenant should do the trick. Ideally implement a switch to choose between members and transitiveMembers

image

Observed Behavior

Currently only users directly added to the group are returned when searched for. Users added to a nested group are not found.

Steps to Reproduce

  • Create a webpart with peoplepicker control
  • Specify a groupid-string from a security group with both users fromnested security group and users directly added to the group. Only users directly added to the AD group are returned when searched for.
@ghost
Copy link

ghost commented Mar 29, 2022

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

@AJIXuMuK
Copy link
Collaborator

Thank you @RicoNL for reporting and implementing this one!

@AJIXuMuK AJIXuMuK added status:fixed-next-drop Issue will be fixed in upcoming release. and removed Needs: Triage 🔍 labels Apr 19, 2022
@joelfmrodrigues joelfmrodrigues added this to the 3.8.0 milestone Apr 28, 2022
@AJIXuMuK AJIXuMuK mentioned this issue May 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:fixed-next-drop Issue will be fixed in upcoming release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants