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

Is Directory.Read.All permission sufficient to enable Group sync feature of AAD plugin? #133

Open
vsalunkhe1988 opened this issue Jun 1, 2022 · 3 comments

Comments

@vsalunkhe1988
Copy link

Hi, As per the documentation https://github.com/hkamel/sonar-auth-aad/wiki/Group-Sync to enable group sync we need to allow "Directory.AccessAsUser.All" for the application under the API permissions in AAD. Our Active directory architecture board is bit hesitant on allowing such permission as it has more privilege's than just reading groups and underlying members.
So is "Directory.Read.All" permission would be sufficient to enable Group sync feature of AAD plugin?

@vsalunkhe1988
Copy link
Author

Also do we need to configure the plugin with Client ID and Client Secret in order to have group sync in place?

@BevanG
Copy link

BevanG commented Jun 22, 2022

I've just configured mine and Directory.Read.All looks like it's sufficient. And yes you need ID and Secret otherwise the application has no way to authenticate to AzureAD

@srvrguy
Copy link
Collaborator

srvrguy commented Aug 2, 2022

I know MS has updated permissions for some of these calls, so I'll do some testing as soon as I have time to determine the best/lowest permissions for the calls we make.

For reference, we're using the /user/{id}/transitiveMemberOf call, which is documented along with needed permissions at https://docs.microsoft.com/en-us/graph/api/user-list-transitivememberof

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

No branches or pull requests

3 participants