ClaimsAuthenticationManager not called

Question

I am having a strange problem with the WIF ClaimsAuthenticationManager. I registered the custom implementation of ClaimsAuthenticationManager in the web.config file:

<identityConfiguration> <claimsAuthenticationManager type="<namespace>.CustomClaimsTransformer,<assembly>" /> <claimsAuthorizationManager type="<namespace>.CustomAuthorisationManager,<assembly>" /> .... 

When I run the application in IISExpress, the ClaimsAuthenticationManager authentication method is called. However, it has not been called since I deployed the application on IIS 7.5.

Is there any configuration that needs to be done?

Answer 1

In the system.webserver part of your web.config, the ClaimsAuthorizationModule parameter is set,

eg,

 <add name="ClaimsAuthorizationModule" type="Microsoft.IdentityModel.Web.ClaimsAuthorizationModule, Microsoft.IdentityModel, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> 

Answer 2

For .NET 4.5, you should add this:

 <add name="ClaimsAuthorizationModule" type="System.IdentityModel.Services.ClaimsAuthorizationModule, System.IdentityModel.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" /> 

Answer 3

RequestsAuthenticationManager does not start automatically. This requires a plumbing code if they do not use WS-Federation.

You can do this in the PostAuthenticateRequest event handler for HttpApplication.

A good example is in the project http://github.com/thinktecture/Thinktecture.IdentityModel.45 . Find the ClaimsAuthenticationHttpModule.cs claim that calls it.