[GLASSFISH-3850] Changing default realm does not indicate that a server restart required Created: 09/Nov/07  Updated: 25/Apr/14

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: 9.1pe
Fix Version/s: future release

Type: Bug Priority: Minor
Reporter: r_sudh Assignee: JeffTancill
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 3,850
Status Whiteboard:



When using the web based Admin Console, changing the Default Realm under
Configuration > Security does not indicate that the server needs to be restarted
for the change to take affect.

Either the GUI needs to display the "Restart required" warning message or maybe
this is a bug in the Security module where the change is not being applied right

Comment by Anissa Lam [ 12/Nov/07 ]

I believe changing Default Realm doesn't require server restart. Using CLI, i
did 'list-domains' and it also doesn't say server require restart.

I am transferring this to 'security'.
If changing default realm shouldn't require server restart, then what the user
reported here is expected and is not a bug.

If changing default realm really require server restart, then whatever is told
to GUI and CLI is wrong, someone needs to fix this.

Either way, this is not a GUI issue.

Comment by basler [ 12/Nov/07 ]

Not a show stopper for 91ur1

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by Scott Fordin [ 18/Mar/11 ]

Added topic under "Restart Required" umbrella issue (http://java.net/jira/browse/GLASSFISH-16040) in 3.1 Release Notes.

Comment by Tom Mueller [ 06/Mar/12 ]

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

Generated at Thu Mar 30 12:48:35 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.