locked
iclaimsidentity and predicate building RRS feed

  • Question

  • User1080785583 posted

    I follow microsofts progress on the identity model and have come to understand that there is no perfect setup for the mscorlib claimsidentity. what I do want, is something that I can extend myself yet not have to worry about getting the .net framework 5.0 or 7.5 for that matter, that could contain the next version of IIdentity and IPrincipal and IClaimsIdentity and IClaimsPrincipal. 

    That being said, I am curious if there is a methodology that does not depend on yet another dll. I only wish to extend current features that microsoft provides out of the box with the new identity, but allow me to use the core library and not download yet another third party implementation of identity.

    Example is, I would provide my application an Interface. Based on that Interface, at runtime, my activator.create would then allow me to use some depencency injection to allow my application to have dynamic authorization mechanisms that rely on the .net framework and make use of mscorlib. 

    I have read up on thinktexture and other third party dlls, but the core problem with this approach is you are yet again relying on their implementation, which is absorbed by microsoft eventually, which is then released into mscorlib for the masses. I will continue to ponder the Thread.CurrentPrincipal and await more abstractions. 

    One day I am hoping there is a way to generate Expression<Func<CurrentPrincipal,bool>> that are composed of my identity. Then I would be able to use another language concurrentl with my task, like predicate building, instead of a hundred functions that do the same thing the identity model has done for the last 10 years of my programming life.

    Suggestions?

    -Lost

    Tuesday, April 8, 2014 2:40 AM