admin@glassfish.java.net

masterpassword testing

From: Elena Asarina <elena.asarina_at_oracle.com>
Date: Thu, 02 Dec 2010 11:35:44 -0800

Hi All,

I just want to clarify that for my clustering tests, I'm using a
default domain without a password. 2.1 CLI tests includes
masterpassword tests. On the last meeting Joe asked about current status
of the masterpassword testing. Please see bellow answers from the
involved people.

Thank you,

Elena

Sankar wrote:

"If you really want to test masterpassword , that should be part of the
admin security testing, where you would create a domain with custom
masterpassword and use commands to change masterpassword and make sure
the domains startup with correct masterpassword. Same goes with
adminpassword. However these tests are manual since the new passwords
were always given interactively and tonga had problems with automating
these interactive tests.

The adminpassword tests were automated and can be found here,
appserver-sqe/pe/admincli/tonga/testbase/adminpassword but it won't
since tonga doesnot handle the interactive password with asadmin. "

Lidia wrote:

"There was no plan to port server lifecycle tests, since you were doing
a great job covering this area in your tests and it was not trivial to
port those...

Also, as Sankar pointed out, domain is created by every module in
current CLI suite. The only issue is that masterpassword is always the
default one: changeit. It may be good to add a test using different
masterpassword."