This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
i know you've got Windows and HttpContext identities supported OOTB for IAuditInfoStrategy. but i'm not sure about "WindowsIdentity and HttpContext cover the majority of Web and Windows scenarios" (from your blog post). Just an idea - since you're focusing on distributed WCF scenarios for 4.0 have you considered including a WCF-friendly IAuditInfoStrategy implementation OOTB? Something like Thread.CurrentPrincipal.IIdentity.Name - that would work fine for those of us that bother setting custom Principals in WCF? Or even something that's Claims-friendly? I'm using WIF to provide an IClaimsPrincipal - and then referencing that in my custom IAuditInfoStrategy. by the way, while we're talking about custom IAuditInfoStrategy, it's kind of weird that I can specify a custom auditinfo thingy in config but I can't also set in config which concrete IAuditInfoStrategy to use. I tried specifying auditInfoStrategyClass in config but that just blew up. So each client of the same shared model has to specify it's own auditinfostrategy to use when newing up the LS context. It would make more sense to me to do the same as custom naming strategies and provide the type to LS directly in the config. |
|
|
Thanks, that's an excellent suggestion about WCF principals, and we'll see if we can sneak it into 4.0. We'll also try to add configuration file settings for some of the stuff that doesn't have them at the moment, including the custom timestamp and audit info classes -- thanks for the reminder. |
|