Author: ApercuOnline | Posted on: 12/20/2008 5:39:15 PM | Views : 284

If that subject wasn't confusing enough for you...  This is what I'm trying to do.
I have multiple applications in their own databases for portability and modularity.  They are operating on the same website.  When I log into one of the applications and then browse on over to another it shows that I am logged in and pulls identity information from the security ticket.  What I truly want to be able to do is keep the roles of the applications seperate but usable so I can use the web.config per directory to restrict browsing.  Is that possible?  If not, what is your suggestion and path to implementation?  I've been coding in circles on this one.  I fear I will have to do a per page verification on load by pulling the applicationID associated with the userID in the membership providerkey.
 
I'm using 2 datastores for 2 sqlmembership providers.  I have CustomIdentity and CustomPrinciple objects  in pl ...

Go to the complete details ...