I encountered this weird behavior while trying to get identities from Azure DevOps.
While this piece of code "almost" returns what I want:
var identities = await identityHttpClient.ListGroupsAsync(new Guid[] {<ScopeOfCollectionParent>});
I found out that some informations were missing, like the subject descriptor.
So I tried an alternative by querying the ReadIdentities method, using the previously obtained ids:
var identities = await identityClient.ReadIdentitiesAsync(new List<Guid>(ids), includeRestrictedVisibility: true);
I got the missing subject descriptors but found out that some identities were not resolved like [TEAM FOUNDATION]\Enterprise Users and [TEAM FOUNDATION]\Security Service Group.
Is there anybody out there who can explain me these bahaviors?
As much as possible, I would like to avoid multiple calls to IdentityHttpClient or GraphHttpClient.
Thanks.
Hi,
I encountered this weird behavior while trying to get identities from Azure DevOps.
While this piece of code "almost" returns what I want:
var identities = await identityHttpClient.ListGroupsAsync(new Guid[] {<ScopeOfCollectionParent>});I found out that some informations were missing, like the subject descriptor.
So I tried an alternative by querying the ReadIdentities method, using the previously obtained ids:
var identities = await identityClient.ReadIdentitiesAsync(new List<Guid>(ids), includeRestrictedVisibility: true);I got the missing subject descriptors but found out that some identities were not resolved like [TEAM FOUNDATION]\Enterprise Users and [TEAM FOUNDATION]\Security Service Group.
Is there anybody out there who can explain me these bahaviors? As much as possible, I would like to avoid multiple calls to IdentityHttpClient or GraphHttpClient. Thanks.