Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-6000

Accessing XUI through a FQDN that is resolvable but not mapped throws an internal server error

    Details

    • Sprint:
      Sprint 86 - Team Tesla, Sprint 88 - Team Tesla, Sprint 89 - Team Tesla
    • Support Ticket IDs:

      Description

      Install OpenAM 12.0.0 as openam.example.com:18080/openam
      Check it can be accessed correctly through openam.example.com:18080/openam/XUI/#login

      Create an entry for the FQDN notmapped.example.com in /etc/hosts
      Restart browser
      Access notmapped.example.com:18080/openam/XUI/#login

      The response will be a HTTP500 (due to OPENAM-5999 it will actually show a hanged page displaying Loading ...).

      Expected: should use the default FQDN and display openam.example.com:18080/openam/XUI/#login

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                phillcunnington Phill Cunnington
                Reporter:
                nathalie.hoet Nathalie Hoet
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: