[OPENAM-6000] Accessing XUI through a FQDN that is resolvable but not mapped throws an internal server error Created: 18/May/15  Updated: 20/Nov/16  Resolved: 07/Jul/15

Status: Resolved
Project: OpenAM
Component/s: XUI
Affects Version/s: 12.0.0, 12.0.1
Fix Version/s: 12.0.2, 12.0.3, 13.0.0

Type: Bug Priority: Major
Reporter: Nathalie Hoet Assignee: Phill Cunnington
Resolution: Fixed Votes: 0
Labels: AME, TESLA, release-notes
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by OPENAM-5999 XUI hangs with "Loading ..." when rec... Resolved
Relates
relates to OPENAM-6340 XUI needs to support DNS/Alias behavi... Open
relates to OPENAM-6293 XUI freezes at startup when serverinf... Resolved
Target Version/s:
Sprint: Sprint 86 - Team Tesla, Sprint 88 - Team Tesla, Sprint 89 - Team Tesla
Support Ticket IDs:
Verified Version/s:

 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



 Comments   
Comment by Phill Cunnington [ 21/May/15 ]

There is definitely a XUI issue as the XUI should not hang. From talking with Phil Ostler [X] it seems the XUI issue is probably related to a race condition when loading the XUI.

There is also a server-side fix for the server when routing a REST request which is using an unmapped DNS alias should default to the root realm.

Comment by Supporto Applicativo [ 21/May/15 ]

In case you should need, there are other test cases causing the XUI to hang:

  • insert the same Realm/DNS Alias value both in a SubRealm and in the Top Level Realm, then try to login with the XUI to the subrealm (see case 7320)
  • remove or insert a non existing key alias in Core Auth Settings - Organization Authentication Certificate Alias, then try to login with XUI (see bug 6003)
    Both these tests generate an Internal Server Error.

Anyway, there other cases where the XUI does not hang in case of an Internal Server Error.

Comment by Phil Ostler [X] (Inactive) [ 03/Jul/15 ]

There is an XUI issue here involving the applications startup sequence and the i18n system not being initialised before an attempt to use it. This is a side effect of the server returning 500 and has been moved into a separate bug (see linked issues)

Comment by Nathalie Hoet [ 07/Jul/15 ]

I don't believe this is a duplicate of OPENAM-5999. OPENAM-5999 is about XUI hanging when it faces an issue.
This one is that if FQDN is not mapped to a DNS alias, it should return the top realm and not a 500 (not a 401 either).

Comment by Phill Cunnington [ 07/Jul/15 ]

Added check in realm routing to ensure DNS alias is mapped correctly

Comment by Peter Major [X] (Inactive) [ 16/Sep/15 ]

Backported to 12.0.3 with R15736

Comment by Nemanja Lukic [ 02/Oct/15 ]

Verified in: OpenAM 12.0.2 Build 15797 (2015-September-21 17:41)

Generated at Mon Oct 19 15:51:42 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.