I have just started experimenting with WIF for a new application I'm writing. So far I have managed to get the LocalSTS working and setup my web.config to enable federated authentication against the LocalSTS. My plan is to use the LocalSTS for now and worry about implementing a custom STS later.
I would like to use the federated authentication to authenticate the user, and once they are authenticated, authorize them to perform various actions internally. so, the STS will authenticate, and the application will authorize internally.
To do this, I will need to store the authorized actions for each user (possibly hundreds of unique actions) in my app database, and read those and cash them once a user starts a new session.
What I am wondering is, how do I map a User that was authenticated using federated authentication to a unique user id that exists in my db, while still keeping the application agnostic to the STS I use (be it ADFS, open auth etc.)?
nameidentifier token seems like a good candidate, but then I read that SAML 2 replaces that with a different token.
Am I approaching this completely the wrong way? am I missing something?
Any help would be greatly appreciated.