Issue Details (XML | Word | Printable)

Key: GLASSFISH-16149
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Joe Di Pol
Reporter: easarina
Votes: 0
Watchers: 0

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

Created a domain with a master password, start-cluster failed

Created: 03/Mar/11 03:13 PM   Updated: 17/Oct/12 08:19 PM
Component/s: admin
Affects Version/s: 4.0
Fix Version/s: future release

Time Tracking:
Not Specified

Issue Links:

Tags: ee7ri_cleanup_deferred
Participants: easarina, Joe Di Pol, Nazrul and Tom Mueller

 Description  « Hide

Executed steps that were described in the umbrella bug 16146.

Then executed start-cluster:
asadmin --passwordfile ./password.txt --port 9999 --host localhost --user admin start-cluster --verbose=true c1
start-instance in9
in9: Could not start instance in9 on node localhost-domain12 (localhost).

Command failed on node localhost-domain12 (localhost): CLI801 Instance is already synchronized
Command start-local-instance failed.

The Master Password is required to start the domain. No console, no prompting possible. You should either create the domain with --savemasterpassword=true or provide a password file with the --passwordfile option.

To complete this operation run the following command locally on host localhost from the GlassFish install location /opt/glassfish3:

asadmin start-local-instance --node localhost-domain12 --sync normal in9

The command start-instance failed for: in9
Command start-cluster completed with warnings.

The password.txt file had such content:


Tom Mueller added a comment - 17/Oct/12 08:19 PM

Marking the fix version field as "future-release". This is based on an evaluation by John, Michael, and Tom WRT to the PRD for the Java EE 7 RI/SDK. This issues was deemed to not be a P1 for that release. If this is in error or there are other reasons why this RFE should be targeted for the Java EE 7 RI/SDK release, then change the fix version field back to an appropriate build.

Nazrul added a comment - 02/May/11 03:16 PM

GlassFish 3.1 is behaving as expected. We never send master password over the wire. If user sets a master password, then 3.1 offer the following options:

1) Use create-local-instance --savemasterpassword option to save the master password locally
2) Use change-master-password --savemasterpassword option to save the master password locally

Converting these 3 issues to Improvement to investigate if we can make life any easier without compromising security.

Joe Di Pol added a comment - 22/Mar/11 10:58 AM

In order to have this work start-instance (and start-cluster) needs to support accepting AS_ADMIN_MASTERPASSWORD and pass it to start-local-instance via stdin (like is done with the security token).

Currently GlassFish never passes the master password over the network – so we would need to make a conscious decision to do that before implementing this fix.

Considering this for 3.2

easarina added a comment - 09/Mar/11 01:11 PM

I was wrong, it still doesn't work with the absolute path to passwordfile.

easarina added a comment - 08/Mar/11 07:38 PM

When I've used an absolute path to the passwordfile, start-cluster command started to work. But start-instance still did not work with the absolute path.

Tom Mueller added a comment - 03/Mar/11 03:36 PM

Is the password file not being passed through SSH to the start-local-instance command?

See similar issue that was filed for start-instance (16147)