People Service ResolvePrincipals does not resolve SharePoint groups when the PrincipalType is All and SharePoint is using claims based authentication
I'm updating some legacy code which relies on the People service. SharePoint groups do not resolve on a webapplication in SP2013 with the authentication provider set to Claims Based Authentication ...
So my problem is this: I have created a Sharepoint Group and added a New User, which in fact is an Active Directory Group. Now I loggin using an account from this Active Directory Group. I need this ...
I want to rename SPPrincipals that are ADGroups. I've tried with $SPFarm = Get-SPFarm #$SPFarm.MigrateGroup("loginName", "newLoginName") $SPFarm.MigrateUserAccount("loginName", "newLoginName", ...
When/why does SPUtility.ResolvePrincipal return a non-null SPPrincipalInfo with a PrincipalId of -1 ? I can manually assign rights to the user through the web interface. The user resides in an active ...
Context I have a List<SPPrincipal> that is a mix of SPGroup, SPUser and AD Users. Problem I'm trying to find out how to determine if an SPPrincipal I have is an SPUser, SPGroup or an AD ...
I have a complex application that have several field of type UserMulti. These fields can accept either SPUser or SPGroup or a combination of both kind. I have in my code the ID and the name of a ...