Uploaded image for project: 'OpenAM Agents'
  1. OpenAM Agents
  2. AMAGENTS-1571

Alternative Agent Port Number not working in a LB env when sso cookie is present

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.1
    • Fix Version/s: 5.0.1.0, 3.5.2, 5.5.0.0
    • Component/s: J2EE Agents
    • Labels:
    • Environment:
      Tomcat 7.0.79 / JDK 1.8.0_162 with haproxy
    • Target Version/s:
    • Verified Version/s:
    • Support Ticket IDs:

      Description

      Alternative agent port name is not used in a load balanced environment, when sso cookie is present.

      Steps to create:

      1) Setup the Java Application Server agent to behind the load balancer/haproxy and make sure lb port is different from Java Application server port, like lb.example.com:82 and agent.example.com:9090.

      2) Follow the procedure documented at https://backstage.forgerock.com/docs/openam-jee-policy-agents/3.5/jee-users-guide/#lb-configure-agent sections 3.5 AND 3.6

      3) Open a new browser window, clear cache and access the protected application instance url like http://agent.example.com:9090/agentsample. After authentication the browser will be redirected to load balancer application url, like http://lb.example.com:82/agentsample.

      4) In the same browser open a new browser tab, access the protected application instance url like http://agent.example.com:9090/agentsample.  

      Expected behavior: The browser should stay at the load balanced URL like http://lb.example.com:82/agentsample

      Current behavior: The browser redirected to the application server instance url http://agent.example.com:9090/agentsample

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kamal.sivanandam@forgerock.com Kamal Sivanandam
              Reporter:
              steve.nolan Steve Nolan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: