After you upgrade SharePoint 2010 to SharePoint 2013, people lose permissions to the site and how to resolve it. The reason and solution for permission lost after the upgrading

There was a problem yesterday when a Web site was upgraded from SharePoint 2010 to SharePoint 2013, people were unable to log in and had to be re-empowered to sign in, which was a hassle.

Reason: Is the issue of authentication mode. In SharePoint 2010, when you create a new Web application through central Administration, you will find that two different authentication methods are available, the first of which is classic Auth (which is what we call Windows Authentication in general), The other is claim base auth. At that time, claim base certification method Microsoft has not been strongly recommended, so the new Web application is mostly based on the most basic Windows certification.

When it comes to SharePoint 2013, Microsoft has begun to strongly recommend the claim base authentication method, and in the new Web application has removed the choice of Windows authentication interface, and the default directly to all the Web Application are certified using the claim base method. That's why there might be "i:0#.w|" in front of our username in SharePoint The reason for this symbol.

And it is the above reasons, resulting in the upgrade after the personnel have no authority. Because 2010 of the site uses Windows authentication, 2013 of the sites are certified with the claim base. Of course specific is not the reason you are the two versions of SharePoint Web application are known.

Workaround:

The first: In SharePoint 2010, change the authentication mode to claim base, and then revert to SharePoint. (This method I think is not very desirable, because to try to preserve the integrity of the original system, if the failure is not good.) ）

The second method:

1. Use the command line to create a new Web application that is certified as Classic Auth (Windows certified) in a SharePoint 2013 environment.

New-spwebapplication-name "Classicauthapp"-port 100-applicationpool "Classicauthapppool"-ApplicationPoolAccount ( Get-spmanagedaccount "<domainname>\<user>")

Be careful to modify the above parameters with your own name and port.

2. Bind the database of your SharePoint 2010 site to SharePoint 2013 new Web application above

Mount-spcontentdatabase "<ContentDb>"-databaseserver "<DbServer>"-webapplication Http://webappurl

3. How to convert SharePoint 2013 restored Web application to claim base authentication

　　

Convert-spwebapplication-identity <yourWebAppUrl>-to claims-retainpermissions [-force]

After you upgrade SharePoint 2010 to SharePoint 2013, people lose permissions to the site and how to resolve it. The reason and solution for permission lost after the upgrading