SharePoint Server 2010 incorporates a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory® directory services, LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. This model uses claims-based authentication and a new product, code-named “Geneva.” Claims-based authentication is built around the concept of an identity and is based on standards — WS-Federation, WS-Trust — and protocols like the Security Assertion Markup Language (SAML).
Videos
Introducing SharePoint Security
SharePoint Server 2010 incorporates a new, more powerful and flexible authentication model that works with any corporate identity system, including Active Directory® directory services, LDAP-based directories, application-specific databases, and new user-centric identity models such as LiveID. This model uses claims-based authentication and a new product, code-named “Geneva.� Claims-based authentication is built around the concept of an identity and is based on standards — WS-Federation, WS-Trust — and protocols like the Security Assertion Markup Language (SAML).
Introduction to Claims based Security
Claims-based identity provides a common way for applications to acquire identity information from users inside their organization, in other organizations, and on the Internet. Identity information is contained in a security token, often simply called a token. A token contains one or more claims about the user. Think of it as metadata about the user that stays with them throughout their session.
Creating a Custom Claim Provider
Claims-based identity provides a common way for applications to acquire identity information from users inside their organization, in other organizations, and on the Internet. Identity information is contained in a security token, often simply called a token. A token contains one or more claims about the user. Think of it as metadata about the user that stays with them throughout their session.