Hello everyone,
I was wondering if any one has been able to configure OTM with netegrity proxy server as reverse proxy. Apart from the <nete:forward> tag is there any other specific configuration?
We are not able to get past the logon page.
I've worked with multiple clients in the past to configure OTM SSO with Netegrity, though they had admins who handled the configuration of the product itself. From past experience, can you ensure the following have been done:
Ensure OTM has been configured to work with a reverse-proxy and the URL-prefix is configured
Ensure that Netegrity is configured to key off of this URL-prefix and remove it before passing the URL back to OTM
Ensure that Netegrity is configured to retain session cookies from OTM in order to maintain session integrity
Thanks Chris.
We have done first 2 part you mentioned. but the last part seems to be treaky... OTM put all the cookies with context path as /GC3, in case of reverse proxy this path is changed and hence there is a problem in doing login to application.
I was wondering if any one has done this part in past....
Last time I worked with Netegrity, it was based on Apache 1.x. Now that it's based on Apache 2.x, this may be an issue. Make sure that you're redirecting the cookies via a parameter like the following:
Quote:
ProxyPassReverseCookiePath / /otm55prod/
I've had to do this in the past with Apache 2.x and Joby had a similar issue with the WebSphere Edge Server (also Apache 2.x based). More info is here: