Contents
In classic-mode, SharePoint uses the Windows identity of the user directly. In claims-mode, SharePoint converts the Windows identity into a claims-based identity token that it can pass to other services as appropriate. App authentication and server-to-server authentication rely on claims-based authentication.
Claims-based authentication is user authentication that uses claims-based identity technologies and infrastructure. Applications that support claims-based authentication obtain a security token from a user, rather than credentials, and use the information within the claims to determine access to resources.
To migrate to claims authentication, see Migrate from classic-mode to claims-based authentication in SharePoint 2013. Recreate included paths. Recreate quota templates. Configure email settings for the web application.
Can a content database be upgraded in SharePoint 2013?
However, for SharePoint 2013, the process does not upgrade the site collections. When you attach a content database, for a web application that spans multiple content databases, make sure that you attach the content database that contains the root site collection first.
Which is the default authentication for SharePoint 2013?
Because claims-based authentication is now the default option for SharePoint 2013, you must use PowerShell to create a web application that uses Windows Classic authentication.
To migrate a claims-based SharePoint 2010 Products web application to SharePoint 2013 In SharePoint 2013, create a claims-based web application. Attach the two existing SharePoint 2010 Products content databases to the newly created SharePoint 2013 claims-based web application.