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

allow service_principals and groups to appear in group_members output #1506

Closed
kent007 opened this issue Mar 21, 2024 · 0 comments · Fixed by #1507
Closed

allow service_principals and groups to appear in group_members output #1506

kent007 opened this issue Mar 21, 2024 · 0 comments · Fixed by #1507
Labels
has_pr PR fixes have been made medium_priority Medium priority

Comments

@kent007
Copy link
Contributor

kent007 commented Mar 21, 2024

SUMMARY

Currently, the modules for AD group manipulation only return membership using the transitive_members property, which collapses nested groups. Additionally, due to a known issue in the graph API, service principals are not returned in queries for any kind of group member. The only way to view service principals is by querying the group object and expanding the members property explicitly.

We should add a flag that forces group_membership return properties to be sourced from the expanded members property, which will properly expose nested groups and service principals. This flag will default to false to preserve compatibility with the existing roles.

ISSUE TYPE
  • Feature Idea
COMPONENT NAME

azure_rm_adgroup_info
azure_rm_adgroup

ADDITIONAL INFORMATION

See example invocation below

  azure.azcollection.azure_rm_adgroup_info:
    object_id: "xx-yy-zz"
   return_group_members: true
   raw_membership: true # <-- new flag that specifies the returned members should include service principals and not be transitive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has_pr PR fixes have been made medium_priority Medium priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants