Hi all,
I am responsible for upgrading several instances of liferay running on a single tomcat servcr to 4.2.0 from 4.0.0RC1. After 2 full days of working, I have all 5 of our instances set up. Also part of the upgrade was implementing CAS SSO. Alright, here's the problem.
I have a root.xml context that runs my default instance of liferay. I can go to root, it loads, I see all my portlets no problem, and I can manipulate them the way I would expect.
Alright, now comes my problem. Lets say we have instance 2 of liferay, which is basically a copy and paste of root, changing the following:
localhost/ROOT.xml
< Context path="" docBase="correct_path_to_root" debug="0" reloadable="true" crossContext="true" >
< Other options that work, (LiferayPool, MailSession, Realm) >
< /Context >
web.xml :
< context-param > < param-name > root_path < /pa.. > < param-value > / < /param.. > < /con... >
< context-param > < param-name > company_id < /pa.. > < param-value > base_comp < /param.. > < /con... >
portal-ext.properties:
portal.ctx=/
------------------------
localhost/jeod.xml:
< Context path="" docBase="correct_path_to_jeod" debug="0" reloadable="true" crossContext="true" >
web.xml :
< context-param > < param-name > root_path < /pa.. > < param-value > /jeod < /param.. > < /con... >
< context-param > < param-name > company_id < /pa.. > < param-value > jeod_comp < /param.. > < /con... >
portal-ext.properties:
portal.ctx=/jeod
Those are my main differences. Ok. So if I go to https://webserver/jeod, i go immediately to my sso page, and log in correctly. I then get redirected back to https://webserver/jeod and go to my main page. ALL portlets now show red text and "You do not have the roles required to access this portlet"
If I now try to log into ROOT, I am able to log into https://webserver/ go into CAS, get redirected, and all portlets show up as intended.
Now I go back to https://webserver/jeod (I am already logged in) and all the portlets show up now. Lets say I now click on enterprise admin->Users... I would expect to be taken to https://webserver/jeod/c/portal.... and go into my jeod enterprise admin portlet. HOWEVER, what actually is currently happening is I'm being taken to https://webserver/c/portal...
For some reason, all my portlets on the other instances other than root are trying to access the ROOT for permissions and everything. I can also tell that the portlets that are showing up under /jeod are acutally portlet instances of root (I can see from an expanded enterprise admin some users that I know are on root, but not jeod)
I could greatly use some help here. Has anyone had the same problem? What was your solution?
Thanks in advance for response.
Please sign in to flag this as inappropriate.