I am implementing a custom login system using the standard ASP.net membership system (I can't use the Umbraco membersip because I need to authenticate against an existing database on our network).
I now need to hook this into my Umbraco site so the entire site is secured (Site 2). The problem is that we have a single instance of Umbraco hosting multiple sites, and as it's a single instance of Umbraco (1 web app) obviously all these sites share the same web.config.
Here is an example:
Umbraco - Site 1 - Site 2 <--- I want to wrap the login system around this site only - Site 3
Does anyone have any ideas of how to achieve this?
Easiest solution would be to split them out into multiple Umbraco instances ;).
What I would do is create a custom membership provider, role provider, etc which checks the host name and then branches internally to the right underlying provider. I'd set up the custom membership provider (to your external store) in the web.config with a different provider key and inherit from the Umbraco ones.. When the login request comes in you then pass it off to the right named membership provider.
Asp.net membership
Hi
I am implementing a custom login system using the standard ASP.net membership system (I can't use the Umbraco membersip because I need to authenticate against an existing database on our network).
I now need to hook this into my Umbraco site so the entire site is secured (Site 2). The problem is that we have a single instance of Umbraco hosting multiple sites, and as it's a single instance of Umbraco (1 web app) obviously all these sites share the same web.config.
Here is an example:
Umbraco
- Site 1
- Site 2 <--- I want to wrap the login system around this site only
- Site 3
Does anyone have any ideas of how to achieve this?
Hope this makes sense?
Thanks!
Easiest solution would be to split them out into multiple Umbraco instances ;).
What I would do is create a custom membership provider, role provider, etc which checks the host name and then branches internally to the right underlying provider. I'd set up the custom membership provider (to your external store) in the web.config with a different provider key and inherit from the Umbraco ones.. When the login request comes in you then pass it off to the right named membership provider.
Thanks for the reply Slace.
Let's say I can't split them out :) how would you achieve this ?
Edit: sorry I didn't read your reply properly... Thanks!
is working on a reply...