This post is as per beta version, there could be some changes with RTM version.
What’s new in SharePoint 2013 for authentication, authorization, and security
The following are some of the enhancements added to SharePoint 2013 Preview:
- User sign-in
- Services and app authentication
SharePoint 2013 Preview includes improvements in claims infrastructure and authentication features that enable new server-to-server and app authentication scenarios.
In SharePoint 2010, we had to choose between two options when creating a Content Web Application – to use Classic mode Authentication or Claims-based Authentication. Now in SharePoint 2013, Claims-based authentication mode is the default authentication method. You cannot from the web interface create content web applications using Classic mode. Classic-mode authentication is deprecated and can be managed only by using Windows PowerShell.
The app authentication and server-to-server authentication features of SharePoint 2013 Preview require claims-based authentication along with a lot of other features.
Find resources about user authentication, server-to-server authentication, and app authentication to help you understand and plan for authentication in SharePoint 2013 Preview.
Describes the steps to configure Security Assertion Markup Language (SAML)-based claims authentication using Active Directory Federation Services (AD FS) 2.0.
Describes the steps to configure forms-based authentication using a Lightweight Directory Access Protocol (LDAP) membership provider.
Provides steps to configure server-to-server (S2S) authentication with another server that uses the S2S protocol.
Information about the administrative and service accounts that are required for an initial SharePoint 2013 deployment.
Get an overview of People Picker and links to topics about how to plan for People Picker in SharePoint 2013.
This script produces a text file report of which items have been unique secured and which Active Directory users and groups have been granted access, based on the user domain specified. The report details whether the user or group has been granted rights directly, or if the user has been granted rights by membership to a SharePoint group though it does not identify if a user has been granted rights based on their membership to an AD Group which in turn has been added to a SharePoint group.
Learn how to deploy a SharePoint 2013 claims provider by using the features infrastructure