Greetings.  Working on version 4.9.4.  I replaced our QA environment with a copy of production.  A major difference is production contains a new portal site using a completely different domain (e.g., base is abc.com, and the second portal is xyz.com).  Everything is working as expected except when I log into the second portal site (xyz.com), the top page control panel is not displaying nor can I access any admin pages?

 

A log entry is added that user has logged in successfully.  I have tried with host and the portal admin user accounts.  It appears the application is not recognizing these users have permission to edit / access pages?  Production is working as expected.  The base portal (abc.com) is working as expected.  The issue is only within the second portal site (xyz.com).

 

Any suggestions?

Thanks but we are working with DNN 4.9.4, which does not have the PortalLocaization table.  I have double checked the portal and user tables and everything mimics the working, production version.  Also, our setup has several child portals under the working base portal and these are working as expected as well.  The issue is only with this one parent portal?

 

One difference is our QA environment is running on IIS6 and production is IIS7; however, this has not caused problems with previous updates or other DNN installations running.  I have running out of troubleshooting ideas..  Any other suggestions would be greater appreciated.  Thanks.

I located the issue.. We are using Blue Tango’s AuthIntegrator module to establish a single sign-on for the base DNN parent (e.g., abc.com) and a custom sub domain site (subsite.abc.com). The required configuration changes for this service requires to include domain=".abc.com" in the