Planning Considerations for Claims Based Authentication in SharePoint 2010

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

Capriole — Wed, 14 Sep 2011 20:13:11 GMT

Should the immutable nature of claims mappings be taken into account when choosing hub vs direct for multiple Partner IdPs/STSes? Hub model implies that you could not change claims mappings for any IdP without deleting and recreating the Hub SPTrustedIdentityTokenIssuer - which could be epic. With direct you would only affect the individual IdP/Partner. I guess you could handle it all with transformations at Hub STS, but only if there were sufficient existing mappings defined for the Hub STS. Seems to indicate careful consideration of claims mappings would be sensible when using Hub model.

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

Mira — Tue, 28 Dec 2010 07:40:39 GMT

Is there a way to implement claim based auth in MOSS 2007. Can we get it customised.

Any help is appreatiated.

Thanks In Advance.

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

madnik7 — Thu, 30 Sep 2010 13:21:32 GMT

Hi vikas

Check following link if you look for a OpenID or Live ID provider for SharePoint 2010 with Claims Based Authentication

www.shetabtech.com/.../SharePointLiveAuth

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

vikas — Fri, 04 Jun 2010 09:23:46 GMT

Great article, and extremelly useful! By the way, do you know if there is any LiveID provider for Claims-Based authentication to be used on SharePoint 2010? I've seen we can still use classic mode and 2007 developments to achieve this but I wonder if there is any improvement in this area.

Thanks!

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

vikas — Fri, 04 Jun 2010 09:23:38 GMT

Thanks!

re: Planning Considerations for Claims Based Authentication in SharePoint 2010

dcday — Thu, 01 Apr 2010 14:23:58 GMT

I like your posts on claims very informative.

One thing I have discovered with claims and BCS is that the certificate used to sign the claim in the oob installation i.e. "SharePoint Security Token Service" is not compatible with Java's metro web services Metro requires the cert to be a CA. I wonder if you have come accross aa way of changing the signing cert. I have tried creating a new cert and calling this command Set-SPSecurityTokenServiceConfig -SigningCertificateThumbprint "413cdbb21c861fcb19c1ee71b9ed2cae748ae10f" which works but the n the entire trust for SP is blown out the window. I imagine there are more steps to be performed but I can't find any documentation.

FYI I am using TAP builds