[GLASSFISH-16606] asadmin enable-secure-admin will not work on additional domains Created: 11/May/11  Updated: 11/May/11  Resolved: 11/May/11

Status: Closed
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: deathtooracle Assignee: Tim Quinn
Resolution: Works as designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified



We have 2 independant domains running on the same server, domain1 was created by the installer and the domain 'ad' through:
/opt/glassfish3.1/bin/asadmin create-domain --portbase 4900 --savemasterpassword=true ad
/opt/glassfish3.1/bin/asadmin enable-secure-admin
does not let one choose which domain to secure, instead it always uses domain1 (port 4848). That means, we cannot secure the admin GUI on domain ad.
We have a high security environment here where unsecured / clear-text admin GUIs are forbidden. So, we cannot use glassfish 3.1 until this bug is resolved.

Please fix or provide us with a working workaround.

Comment by Tim Quinn [ 11/May/11 ]

As with any asadmin command, you must specify the correct admin port on the enable-secure-admin command in order for asadmin to connect to the domain you want.

The default is 4848. You need to specify the correct admin port for your second domain explicitly, using

asadmin --host hostName --port portNumber rest-of-command

The default hostName is the same host where you run the asadmin command, so that part is optional if that's what you want to do.

Comment by deathtooracle [ 11/May/11 ]

Excellent, thank you very very much.

Generated at Sun Nov 29 13:20:28 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.