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

Cannot install web agent if the AM URL does not return 302

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 5.5.0.0, 5.7.0, 5.8.0
    • Fix Version/s: None
    • Component/s: Web Agents
    • Environment:
      AM version does not matter 5.5.1 and 7.0.0.
      This issue is reported not happening in WPA4.
    • Support Ticket IDs:

      Description

      In the wild, it seems that some infrastructure will prevent direct context access to
      say http://openam.example.com/openam and return 404 for this instead
      of getting 302.

      2019-03-21 05:42:39 installation exit because user typed "q" for input
      head request status 404
      

      The issue is that the webagent installation detection needs AMURL to return 302 (or 200) but the problem is that one cannot pass in http://openam.example.com/openam/ and it will cause other API issues.

      Hence this request is to if the is am AM_URL (the code may as well check for AML_URL (with /) prefixed to ensure it is 200 directly to avoid issues).

      Impact: Cannot install AM (unless --forceInstall)

      Workaround:

      Use force install.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            chee-weng.chea C-Weng C
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: