Claims Provider in SharePoint 2010

A Claims Provider in SharePoint 2010 issue claims and pakages claims into securty tokens. how claim wok. first user get the token from claim provider in sp then login into SharePoint 2010. mostly it use for to augment claims and provide name resolution.
Claims augmentation start after user login to Claims Authentication Site. to remeber that the user is running on claim in authentication sharepoint 2010 site.it can be

1 widdows (NTLM(Out of box default.) or Kerberos Protocol)

2 form-Based Auth (by using ASpnet membership role provider framework)

3 Security Assertions Markup Language (SAML) claims (when you log on by using a security token service (STS), such as Active Directory Federation Services (AD FS) 2.0)

like most commonly problem in share point 2010 with search resolve in People Picker for trusted Login Providers. for example if your typing in Seach of public picker to validate user and its not resolving. to solve this Problem in sp2010  you have two ways.
 Custom Claim Provider
http://blogs.technet.com/b/speschka/archive/2010/03/13/writing-a-custom-claims-provider-for-sharepoint-2010-part-1.aspx
Replace the Dfault Claims Provider with your own.

$trusted = Get-SPTrustedIdentityTokenIssuer -Identity "Trusted Login Provider Name Goes Here"
$trusted.ClaimProviderName = “name of your custom claim provider”  //in your claim provider you need to override the SPClaimProvider.Name; use that value here
$trusted.Update();



Reference
http://msdn.microsoft.com/en-us/library/gg251994.aspx
Writte Code for claim  Provider Walkthrough
http://msdn.microsoft.com/en-us/library/ff699494.aspx
Creating Custom Claim Provider
http://msdn.microsoft.com/en-us/library/gg615945.aspx
Case Study
http://technet.microsoft.com/en-us/library/hh427307.aspx
Claim Based Architecture
http://msdn.microsoft.com/en-us/library/hh394901.aspx
http://msdn.microsoft.com/en-us/library/gg552609.aspx
sample
http://blogs.technet.com/b/speschka/archive/2010/03/13/writing-a-custom-claims-provider-for-sharepoint-2010-part-1.aspx

share this post