I have been trying to figure out how to share authentication, membership, profile, and roles between applications. I've read elsewhere that you have to place applications under a parent application, use the same machine code and applicationName in the web.config files. When I put one application under another, I get a message that the application is not configured as an application under IIS, even though it is. I'm using Windows XP Pro and VS 2005. Has anyone been able to get this to work?
Barry
I too have this issue of wanting to share authentication between two virtual directories, one local to the machine and one on a remote share. This would allow a web farm to use local application copies on each server but have a subset of the content of the site on a shared drive on a different NAS server. Problem is that the content on the NAS server needs to fall under the authentication protection of the individual apps on each farm server.
I'll keep looking and any helpful information that I can share I will post here.
Regards!
the way we accomplished this was when you clicked from one application to another, before leaving the first site, it would create a record in a table we called CrossAppAuth that would store the current authentication information. We would then pass the unique id of that record to the next app, which would open it up, and authenticate the user upon page load. Kind of a hack, but that's how we finally got two of our apps so you didn't have to login to both.
0 comments:
Post a Comment