Which Technology Stack Should I Use for Claims-Aware Applications

Question

This is a second attempt with better wording of the problem I'm facing.

I have a simple requirement to implement an application that will allow web applications and standalone services that will be claims-aware (using ADFS). Note that I am talking about windows services in addition to web applications.

Which enabling interoperable technologies should a developer pick?

For the life of me, I can't find a resource that says: to build a claims-aware application using the latest upcoming frameworks, install these packages.

From a framework point of view, I am talking about the following:

Microsoft.IdentityModel
Microsoft.Owin
System.IdentityModel
Microsoft.Asp.Net.Identity

Which should I be using? Alpha / Beta packages are fine.

Thank you, Richard

jonho · Accepted Answer · 2014-03-07T19:46:11.333

2

in .net 4.5 IdentityModel is now part of the core libraries (so it no longer called Microsoft.IdentityModel).

So for your system you would need the following:

System.IdentityModel for the FederationAuthenticationModule (which intercepts and verifies your SAML token submission) and for the SessionAuthenticationModule (which serializes/deserializes your claims.)

To create the claims that you will send between your applciations you would use:

System.Security.Claims

as I mentioned these are both in .net 4.5.

edited Mar 07 '14 at 19:46

answered Mar 07 '14 at 13:51

jonho

1,680
2
19
29

If you know how OWIN and ASP.NET Identity fit in with all this, I'm all ears. – Richard Mar 11 '14 at 05:40
this is good article from brock allen - http://brockallen.com/2013/10/24/a-primer-on-owin-cookie-authentication-middleware-for-the-asp-net-developer/ – jonho Mar 11 '14 at 18:14

score 0 · Answer 2 · answered Mar 07 '14 at 09:16

0

Microsoft.IdentityModel is the one you are looking for.

Microsoft.IdentityModel.Claims for IClaimsIdentity interface.

Microsoft.IdentityModel.Web for WSFederationAuthenticationModule.

answered Mar 07 '14 at 09:16

Melkor S.K

133
1
10

score 0 · Answer 3 · answered Mar 09 '14 at 19:37

0

Yup - System.IdentityModel is the way to go.

Refer: What's New in Windows Identity Foundation 4.5.

If you are wondering what the difference between WIF 3.5 and 4.5 is, refer:

Guidelines for Migrating an Application Built Using WIF 3.5 to WIF 4.5

answered Mar 09 '14 at 19:37

rbrayb

46,440
34
114
174

Which Technology Stack Should I Use for Claims-Aware Applications

3 Answers3