claims-based-identity

I want to change the Authentication Provider from Kerberos to Claim-Based in my SharePoint 2010 Enterprise Edition environment. What problems can occur in my SharePoint environment? I heard that there are problems with the RSS Reader Webpart if the Webpart consumed a feed from my SharePoint. It will probably not be usable with Claim-Based Authentication. Are there other problems like this? You mean that you want to change from classic authentication to claims-based authentication. Claims-based authentication also supports Kerberos (as well as NTLM). Therefore, you shouldn't encounter the

Recently I have started using claim-based authentication on an existing web application. Because the application makes use of jQuery & more notably, the AJAX functions, I have had to alter the handlers not to attempt to redirect the XmlHTTPRequests , and instead return a 403 status which is easier to handle. Here is the FederatedAuthentication.WSFederationAuthenticationModule.AuthorizationFailed event hanlder: protected void WSFederationAuthenticationModule_AuthorizationFailed(object sender, AuthorizationFailedEventArgs e) { //WSFederationAuthenticationModule sam =

Is it possible to share the claims based authentication of a logged in Sharepoint 2010 user with a separate Asp.net application? The following article describes how it was done using Sharepoint 2007 and forms authentication through forms auth and sharing machine keys etc however I cannot find any information regarding the external application consuming the claims authentication that is now used in Sharepoint 2010? Who authenticates the user in SP in your app? In a claims based architecture, you normally would deploy an STS that will authenticate users and issue security tokens (e.g. ADFS).