We currently have a custom Principal and Identity objects that are being used with our CSLA ASP.NET applications. Our corporate website is being converted to use Sitefinity as a CMS. this uses the Membership and profile Providers that are built into ASP.NET.
How in the world do we leverage what we have in CSLA to work in the provider state?
I've done some searching but nothing really hits it from this angle and trying to reverse the logic hasn't gone very well.
I know this post is a little bit old but I want to know how you solve this problem...
The same problem: We are integrating our e-Commerce (that uses CSLA IPrincipal) within sitefinity CMS and it use its own security principal.
Looks like you can't have both working together because each one rely on its own custom principal implementation.
Thanks in advance for any help..comment.. or tip..
Copyright (c) Marimer LLC