2 IIS sites sharing same database, hiding content by User.Identity.Name
Hi there
We have an Umbraco site on our internal network (1) http://staffintranet which uses Windows authentication. We now wish to make the majority (but not all) of the content of this site publicly accessible over the web e.g. (2) http://staffintranet.ourdomain.com using anonymous authentication, while at the same time maintaining http://staffintranet.
Our plan is to maintain all content via the back office on http://staffintranet/umbraco and to create a field on all document types named "InternalOnly". We'd user User.Identity.Name checks in our macros to determine if the user is running site (1) or site (2), and we would amend our navigation macro to hide from nav for (2) when InternalOnly is set. We'd also amend our search for (2) to exclude InternalOnly, and would need to amend our master template to redirect any pages to the home page for (2) (as the pages would be published, we'd just look to avoid people getting to them)
Both (1) and (2) would share the same database and we would set up a job to copy the media and css from (1) to (2) periodically.
Does anyone else have experience of a setting up a similar solution, or can you think of a more graceful way of handling this?
2 IIS sites sharing same database, hiding content by User.Identity.Name
Hi there
We have an Umbraco site on our internal network (1) http://staffintranet which uses Windows authentication. We now wish to make the majority (but not all) of the content of this site publicly accessible over the web e.g. (2) http://staffintranet.ourdomain.com using anonymous authentication, while at the same time maintaining http://staffintranet.
Our plan is to maintain all content via the back office on http://staffintranet/umbraco and to create a field on all document types named "InternalOnly". We'd user User.Identity.Name checks in our macros to determine if the user is running site (1) or site (2), and we would amend our navigation macro to hide from nav for (2) when InternalOnly is set. We'd also amend our search for (2) to exclude InternalOnly, and would need to amend our master template to redirect any pages to the home page for (2) (as the pages would be published, we'd just look to avoid people getting to them)
Both (1) and (2) would share the same database and we would set up a job to copy the media and css from (1) to (2) periodically.
Does anyone else have experience of a setting up a similar solution, or can you think of a more graceful way of handling this?
is working on a reply...