About claims-based authentication The claims-based security model extends traditional authentication models to include other directory sources that contain information about users. This identity federation lets users from various sources, such as Active Directory Domain Services (AD DS), customers via the Internet, or business partners, authenticate with native single sign-on. The model has three components: the relying party, which needs the claim to decide what it is going to do; the identity provider, which provides the claim; and the user, who decides what if any information they want to provide. Microsoft provides a claims-based access solution called Active Directory Federation Services (AD FS). AD FS enables Active Directory Domain Services (AD DS) to be an identity provider in the claims-based access platform. AD FS consists of the following components: AD FS Framework provides developers .NET security logic for building claims-aware  applications, enhancing either ASP.NET or WCF applications. Active Directory Federation Services (AD FS) is a security token service (STS) for issuing and  transforming claims, enabling federations, and managing user access. Active Directory Federation Services (AD FS) supports the WS-Trust, WS-Federation, and Security Assertion Markup Language (SAML) protocols. Active Directory Federation Services (AD FS) can also issue manage information cards for AD DS users. For more information about AD FS, see: Identity & Access  (Windows Server 2012 AD FS 2.1)  Download AD FS 2.0 for Windows Server 2008:  Internet-facing server best practices Implement a strong password policy To reduce the risk of attacks" we strongly recommend that you implement a strong password policy for remote users who are accessing the domain where Microsoft Dynamics CRM is installed. For more information about how to implement a strong password policy in Windows Server, see on Microsoft TechNet and the "Understanding User Accounts" topic in Active Directory Users and Computers Help.
About claims-based authentication The claims-based security model extends traditional authentication models to include other directory sources that contain information about users. This identity federation lets users from various sources, such as Active Directory Domain Services (AD DS), customers via the Internet, or business partners, authenticate with native single sign-on. The model has three components: the relying party, which needs the claim to decide what it is going to do; the identity provider, which provides the claim; and the user, who decides what if any information they want to provide. Microsoft provides a claims-based access solution called Active Directory Federation Services (AD FS). AD FS enables Active Directory Domain Services (AD DS) to be an identity provider in the claims-based access platform. AD FS consists of the following components:  AD FS Framework provides developers .NET security logic for building claims-aware applications, enhancing either ASP.NET or WCF applications.  Active Directory Federation Services (AD FS) is a security token service (STS) for issuing and transforming claims, enabling federations, and managing user access. Active Directory Federation Services (AD FS) supports the WS-Trust, WS-Federation, and Security Assertion Markup Language (SAML) protocols. Active Directory Federation Services (AD FS) can also issue manage information cards for AD DS users. For more information about AD FS, see:  Identity & Access  (Windows Server 2012 AD FS 2.1)  Download AD FS 2.0 for Windows Server 2008: Internet-facing server best practices Implement a strong password policy To reduce the risk of attacks" we strongly recommend that you implement a strong password policy for remote users who are accessing the domain where Microsoft Dynamics CRM is installed. For more information about how to implement a strong password policy in Windows Server, see on Microsoft TechNet and the "Understanding User Accounts" topic in Active Directory Users and Computers Help.
microsoft-dynamics-crm-2013-system-requirements-document.docx