SharePoint Claims authentication resources

 

 

C2WTS test utilityGP0|#48a91ef7-2b39-407e-9351-5ed475401d76;L0|#048a91ef7-2b39-407e-9351-5ed475401d76|Claims;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#6553c9ac-7cd3-4c35-9ee0-494641495101;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​A utility to simulate a service application making use of C2WTS service to convert a UPN into a windows token.
Important Change for Custom Claims Providers in SharePoint 2013 - and Refresh of Some Favorite Claims ToolsGP0|#48a91ef7-2b39-407e-9351-5ed475401d76;L0|#048a91ef7-2b39-407e-9351-5ed475401d76|Claims;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#6553c9ac-7cd3-4c35-9ee0-494641495101;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​there's been a change in SharePoint 2013 when you install a custom claims provider. The IsUsedByDefault property is now set to False by default; in SharePoint 2010 it was True, which means as soon as you installed your custom claims provider everything "just worked". You will now have to go and change this, either after the fact or as part of your claims provider receiver assembly, in order to have your claims provider start working.
Integrating SharePoint 2013 With ADFS And ShibbolethGP0|#48a91ef7-2b39-407e-9351-5ed475401d76;L0|#048a91ef7-2b39-407e-9351-5ed475401d76|Claims;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#6553c9ac-7cd3-4c35-9ee0-494641495101;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​Good description of configuring SharePoint 2013, ADFS 3.0 and Shibboleth
Claims authentication does not validate user (SharePoint 2013)GP0|#48a91ef7-2b39-407e-9351-5ed475401d76;L0|#048a91ef7-2b39-407e-9351-5ed475401d76|Claims;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#6553c9ac-7cd3-4c35-9ee0-494641495101;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 Because SharePoint 2013 recommends claims-based authentication for user access to web applications, this article describes the tools and techniques that you can use to troubleshoot failed claims-based user authentication attempts.
SharePoint 2013 & 2010 Claims EncodingGP0|#48a91ef7-2b39-407e-9351-5ed475401d76;L0|#048a91ef7-2b39-407e-9351-5ed475401d76|Claims;GTSet|#68e31ecf-dbe9-45e0-8a3c-fc6bd6ad0ce6;GPP|#6553c9ac-7cd3-4c35-9ee0-494641495101;GPP|#1b064965-36f6-40b1-a474-78053852e564;GPP|#74f9ea2a-fcec-489f-9ca4-da563b559213 ​A good description of how SharePoint displays identity claims encoding format like i05.t|adfs|david@contoso.com