-
Notifications
You must be signed in to change notification settings - Fork 8
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
When 'Return security-enabled groups only' is checked, no results are returned for Groups #109
Comments
Thank you for reporting this, I will test it soon and let you know if I repro |
It's absolutely a bug, fixed in 5d1f26b |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Yvand : I have installed the latest release and the issue is now resolved. I can now search for users and also security groups. |
Just to be clear, did you mean that it resolved the issue or not (you typed "not resolved")? |
@Yvand : Sorry about my typo. The issue is now resolved. |
* Fix #109 * Update Microsoft.Graph and Microsoft.Identity.Client * Add ConfigureAwait(false) to Task.WhenAll() * Fix bug: set ExcludeMembers instead of ExcludeGuests in new AAD tenant dialog * Better handle scenario when AzureCP cannot get an access token for a tenant * Update CHANGELOG.md * Update Microsoft.Identity.Client and Microsoft.Graph * Update text in AzureCP global admin page * Update CHANGELOG.md * Update NuGet packages
When I check for 'Return security-enabled groups only'. No groups are returned. I have some Azure AD Groups and I do have groups that are synchronized from On-Prem Active Directory on my Dev Farm. I did not work either in V16 or V17 as well.
Here is my AzureCP Settings :
Here are my Claims Settings:
Here are my claim types:
http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name <-- Identifier Claim
http://schemas.microsoft.com/ws/2008/06/identity/claims/role
The text was updated successfully, but these errors were encountered: