I'm following a suggestion from Dominic Cronin on setting up multiple host headers to help demonstrating different users on the same CMS, but I'm stuck at the login pop-up.
As an administrator, I added the following to:
C:\Windows\System32\drivers\etc\hosts
and saved the changes.127.0.0.1 authors.tridion.local
127.0.0.1 admin.tridion.localIn the Site Bindings for SDL Tridion 2011 (my CMS installation) in IIS 7.5, I have:
For authors:
- Type: http
- IP address:
All Unssigned
(i.e. "*") - Port: 80
- Host name: authors.tridion.local
For admins:
- Type: http
- IP address:
All Unssigned
(i.e. "*") - Port: 80
- Host name: admin.tridion.local
(tried other ports, but 80 works fine for multiple headers)
When attempting to visit http://authors.tridion.local
or http://admin.tridion.local
in Chrome, I'm prompted to log in (so the host and IIS setup seems to be partially working), but entering a valid user name and password won't get me past the login pop-up.
Cancelling the login pop-up gives me the IIS error:
HTTP Error 401.2 - Unauthorized
You are not authorized to view this page due to invalid authentication headers.
Additional info:
- Application pool for Site
SDL Tridion 2011
isSDL Tridion 2011
with physical path set toC:\Program Files(x86)\Tridion\web
. This application pool is set to .NET v4.0 asIntegrated
for pipeline mode. - When attempting to log in to one of these additional URLs, my already logged in administrator (on
http://localhost
), will see authorization errors such as/WebUI/Models/TCM54/Services/General.svc/GetItem failed to execute. STATUS (500): System.ServiceModel.ServiceActivationException
.
I'm thinking I'm missing something with the ports (since updated to separate ports), Windows folder permissions, or an appropriate restart. How do I set up separate urls for different users on a Tridion CMS instance/VM?
Update 1:
- I disabled
LoopBackChecks
with regedit and restarted the VM (thanks, Chris). I can at least get past the login pop-ups to see most of the CME in Chrome and IE (after changing IE's security level). - I tried updating the WebRoot's web.config based on Dominic's post, but changes to
multiport/multihostname
underappSettings
,httpModules
,modules
, andserviceHostingEnvironment
were not needed.
Update 2 (part of the solution):
By default, for .NET 4.0, multiple headers for WCF sites in IIS is disabled.
Adding multipleSiteBindingsEnabled="true"
to serviceHostingEnvironment
now lets me browse each url as different users.
<system.serviceModel>
<serviceHostingEnvironment
aspNetCompatibilityEnabled="true"
multipleSiteBindingsEnabled="true">
.\username
worked as well to automatically select the domain.