Issue Details (XML | Word | Printable)

Key: GLASSFISH-12842
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Peter Bower
Reporter: kumarjayanti
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

Admin-GUI startup resets runtime Default Realm to FileRealm incorrectly

Created: 30/Jul/10 02:27 AM   Updated: 06/Nov/13 03:38 PM
Component/s: amx
Affects Version/s: 3.1
Fix Version/s: not determined

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. grab-1.jpg
(63 kB)

2. grab-2.jpg
(69 kB)

3. grab-2.jpg
(69 kB)
Environment:

Operating System: All
Platform: Macintosh


Issuezilla Id: 12,842
Tags: 3_1-exclude
Participants: kumarjayanti, Peter Bower, Peter Butkovic, prasads, sanandal and Tom Mueller


 Description  « Hide

I have a server config where i have set the default-realm attribute on security-service to "ldaprealm".
Everytime i start Admin-GUI then the default realm gets reset to "filerealm" which happens to be the
default when nothing was explicitly given.

If i try to see the value of default-realm in GUI after loading however it does show the correct
value"ldaprealm". But the internal RuntimeValue in Security Realm.java has been changed to "filerealm"

I debugged this and found that the issue is in AMX code. Attached are call stacks when admin gui is
loading to show the issue.

Steps to reproduce :

1. Open Admin GUI and under Configuration->Security set the default realm to something otherthan
filerealm.

2. You can for example create another realm in GUI first (which can be another filerealm with different
name) and set that as the default.

3. Now restart the server and access admin gui in the browser.

After the browser has loaded Admin-GUI, the default realm in the security runtime would be changed
back to original filerealm and not the one created in step 2.

I also notice that the call to Realm.setDefaultRealm() happens many many times during loading of
Admin GUI which seems somehow unnecessary.

Marking as P2 since without this being fixed we are blocked on the Oracle Access Manager integration
where we require the default glassfish realm to be an ldaprealm. And things only work as long as the
Admin GUI is not loaded.



kumarjayanti added a comment - 30/Jul/10 02:28 AM

Created an attachment (id=4613)
call stack 1


kumarjayanti added a comment - 30/Jul/10 02:29 AM

Created an attachment (id=4614)
call stack 2


kumarjayanti added a comment - 30/Jul/10 02:29 AM

Created an attachment (id=4615)
call stack 2


prasads added a comment - 07/Oct/10 04:49 AM

...


prasads added a comment - 07/Oct/10 04:52 AM

Kumar
, does this issue happen now since Admin GUI does not use AMX.


prasads added a comment - 07/Oct/10 04:54 AM

Downgrading to a P3 now.


sanandal added a comment - 08/Oct/10 02:59 AM

...


prasads added a comment - 15/Dec/10 09:27 PM

Excluding this for v3.1 since GUI does not use AMX


prasads added a comment - 20/Feb/11 08:03 AM

Assigning issues to Naman


Tom Mueller added a comment - 06/Mar/12 09:55 PM

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.


Peter Butkovic added a comment - 06/Nov/13 03:00 PM - edited

The same problem is reproducible when connecting with JConsole (via Remote Process only).

Tested with:

  • Glassfish 3.1.2.2.
  • Windows and Linux