Fórum

Problem with prop. web.server.host

thumbnail
Jari Fredriksson, modificado 13 Anos atrás.

Problem with prop. web.server.host

Junior Member Postagens: 27 Data de Entrada: 14/09/10 Postagens Recentes
I'm using LR 6.0.5 on Debian linux. Trying to put that behind Tivoli Access Manager.

portal-ext.properties:
web.server.host = www.servername.tld

I can't click any links on the site, or I can, but I always end up to the front page. I can not log in, I can not select another page.

The problem seem not to be with the Access Manager, as if I set the web.server.host to the actual host serving Liferay, and use it directly, the problem stays.

What might cause this?
thumbnail
Jari Fredriksson, modificado 13 Anos atrás.

RE: Problem with prop. web.server.host

Junior Member Postagens: 27 Data de Entrada: 14/09/10 Postagens Recentes
OK. My real problem is that the Liferay server behind the proxy assigns the LR host name to JavaScript, most like in getUrlHome(). That comes when clicking "Return to site" in Control Panel mostly.

I have configured virtual host, and LR honors that and most everything works. But still the wrong host comes every now and then.

And if I try web.server.host Liferay just does not work at all. Every click sends to front page. This problem is so even without the proxy. Setting web.server.host just renders Liferay unusable.

Do we have a bug (bugs) or did do I something wrong?
ratna prasad kakani, modificado 13 Anos atrás.

RE: Problem with prop. web.server.host

New Member Postagens: 11 Data de Entrada: 02/11/10 Postagens Recentes
hai,

could you help me in integrating liferay to tivoli access manager.

we are trying to integrate using a standard junction with web seal, when we are trying to login

when we try to access ,we are getting login page of TAM, after entering the user-name and password it is redirecting to liferay login page, instead of home page.

i need some help
regards
thumbnail
Jari Fredriksson, modificado 12 Anos atrás.

RE: Problem with prop. web.server.host

Junior Member Postagens: 27 Data de Entrada: 14/09/10 Postagens Recentes
I have integrated Liferay 6.0.5 with Tivoli Access Manager 6.1.1. like this:

I have the root allowed for unauthenticated users.

In TAM pdadmin


pdadmin sec_master> acl create unauth
pdadmin sec_master> acl modify unauth set group iv-admin TcmdbsvaBRrxl
pdadmin sec_master> acl modify unauth set group webseal-servers Tgmdbsrxl
pdadmin sec_master> acl modify unauth set user sec_master TcmdbsvaBRrxl
pdadmin sec_master> acl modify unauth set any-other Trx
pdadmin sec_master> acl modify unauth set unauthenticated Trx
pdadmin sec_master> acl attach /WebSEAL/www.example.com-default/ unauth


That way autentication is not needed for unauth use of Liferay.

Now. When user wants to authenticate, she goes to /c/portal/login

I create an ACL for that, (and also a transparent path junction point).


pdadmin sec_master> acl create Liferay-users
pdadmin sec_master> acl modify Liferay-users set group iv-admin TcmdbsvaBRrxl
pdadmin sec_master> acl modify Liferay-users set group webseal-servers Tgmdbsrxl
pdadmin sec_master> acl modifyLiferay-users set user sec_master TcmdbsvaBRrxl
pdadmin sec_master> acl modify Liferay-users set any-other Trx
pdadmin sec_master> acl attach /WebSEAL/www.example.com-default/c/portal/login Liferay-users


I activate SiteMinder authentication in Liferay. The userid header name is iv-user in WebSEAL.

I activate LDAP import from TAM LDAP (we use Tivoli Directory Server), so that Liferay can get the user info from there, if itself does not know user.

Now liferay works normally, and does not show its own login page. WebSEAL does the authentication, and user is authenticated both in Liferay and WebSEAL.

I hope this helps.