Access Manager behind Proxy server
We have Access Manager 7 on Sun Application Server 8.1 on a box behind Sun Proxy Server 4.0.3 (running in reverse proxy configuration) on a second box. The proxy box is available from the internet (let's pretend it's at proxy.example.com) and responds to https requests only. The app server is not visible from the internet, but is accessible from the proxy (let's pretend it's at http://app.example.com:8181). We also have the Policy Agent installed on the appserver and set up to protect our app. Our problem is as follows:
1. Accessing an app protected by the policy agent via the proxy (e.g. https://proxy.example.com/App1) works fine. The login comes up (still using the proxy address) and once the user logs in the application comes up, also still using the proxy address.
2. Accessing the Access Manager console via the proxy once a user has logged in (as in step 1) also works correctly. All the pages use the proxy address and the user can use the console to say change their password.
3. Accessing the Access Manager console via the proxy without logging in first (by accessing a different protected page) does not work correctly. The server redirects the user to the login using actual address of the app server, which of course is not visible from the outside.
Someone on the forums suggested adding an entry to the fqdnMap in AMConfig.properties file where both the invalid and valid name are the proxy name, but this does not appear to make any difference.
I'd appreciate any insight into why this is a happening and how to fix it.\
Ed
