-
Notifications
You must be signed in to change notification settings - Fork 194
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
SetSiteCollectionAdminsAsync does not consistently work for Groupified sites #1307
Closed
1 task done
Labels
area:admin 📜
Admin library related
Comments
Hi @mloitzl, Br, |
That would be great @mloitzl :-) |
@plamber A quick update A workaround would be to pass ISiteCollectionManager siteCollectionManager = context.GetSiteCollectionManager();
// add the group as admin
string groupClaim = $"c:0t.c|tenant|{securityGroupId}";
List<String> groupAdmin = new()
{
null,
groupClaim
};
await siteCollectionManager.SetSiteCollectionAdminsAsync(context.Uri, groupAdmin); But anyways, @jansenbe I will try to figure out a fix. |
Hi @mloitzl, Best regards, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Category
Describe the bug
If you try to apply one security group to a Groupified SharePoint site using the sharePointAdminLoginNames parameter, the site collection admin is skipped.
Steps to reproduce
When running the code on a Groupified site, the site collection admin is not applied.
Expected behavior
The first entry is not skipped
Environment details (development & target environment)
Latest official SDK version
Additional context
Seems that there is a loop that skips the first application of a Group. A workaround is assigning the group twice.
Thank you for your help
The text was updated successfully, but these errors were encountered: