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

Add support for PIM AAD Group eligibility #254

Closed
wants to merge 4 commits into from
Closed

Add support for PIM AAD Group eligibility #254

wants to merge 4 commits into from

Conversation

oWretch
Copy link
Contributor

@oWretch oWretch commented Aug 11, 2023

This PR provides support for Privileged Management of AAD Groups with Eligible assignments. This implements part of #248.

@oWretch
Copy link
Contributor Author

oWretch commented Aug 11, 2023

As with #253, the tests use an environment variable with default in the test file to use a pre-existing PIM-enabled group.

Had been in one client to try and automate the PIM activation which didn’t work.
@audunsolemdal
Copy link

Any chance for a review @manicminer ?

@oWretch
Copy link
Contributor Author

oWretch commented Feb 25, 2024

A service principal can now activate the PIM groups. I've updated the tests to create the group, and they run successfully under the SP. It just needs to have the following Graph permissions:

PrivilegedAccess.ReadWrite.AzureADGroup
PrivilegedAssignmentSchedule.ReadWrite.AzureADGroup
PrivilegedEligibilitySchedule.ReadWrite.AzureADGroup
Test passes happily 🙂

=== RUN   TestPrivilegedAccessGroupEligibilityScheduleClient
--- PASS: TestPrivilegedAccessGroupEligibilityScheduleClient (18.44s)
PASS
ok  	github.com/manicminer/hamilton/msgraph	19.309s

@oWretch
Copy link
Contributor Author

oWretch commented Mar 6, 2024

Replaced by #277

@oWretch oWretch closed this Mar 6, 2024
@oWretch oWretch deleted the f/pim-group-eligible-schedule branch March 6, 2024 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants