dev@glassfish.java.net

Re: Problems running QLook: Was: HEADS UP: Changes to GlassFish admin CLI ...

From: Marina Vatkina <Marina.Vatkina_at_Sun.COM>
Date: Wed, 22 Feb 2006 17:25:28 -0800

OK. I was able to start the QLook after making the following changes:
a) in the ~/.asadminpass I changed AS_ADMIN_MASTERPASSWORD value to
be the same as the other 2;
b) then made the same change to appserv-tests/config.properties for
master.password.
I didn't change ssl.password (let's see if I needed that also).
Changing only a) doesn't solve the problem.

Now I'd be interested in some explanations of this magic :)

thanks,
-marina

Marina Vatkina wrote On 02/22/06 16:11,:
> Kedar,
>
> How would I change QLook to use this command?
>
> thanks,
> -marina
>
> Kedar Mhaswade wrote On 02/22/06 15:34,:
>
>>Marina,
>> I understand your frustration. Sorry about the same.
>> But there was a bug introduced (6388717) that causes this problem.
>>Prashanth is working on fixing it.
>> For now, could you please do the following:
>>
>>- asadmin start-domain --user <admin-user-name>?
>>
>> Please let me know what happens.
>>
>>Regards,
>>Kedar
>>
>>
>>Marina Vatkina wrote:
>>
>>
>>
>>>Kedar,
>>>
>>>Now it's really bad. How can I run QLook? Whatever I do, it fails
>>>to start a domain.
>>>
>>>I tried:
>>>a) to start a domain with --savemasterpassword=true
>>>b) to do asadmin login (btw, do I need to repeat it after
>>>each restart, as I need to stop a domain to run QLook)
>>>
>>>There are no directions in either the web page
>>>(https://glassfish.dev.java.net/public/GuidelinesandConventions.html#Quicklook_Tests)
>>>or the QuickLook-README.txt under appserv-tests.
>>>
>>>thanks,
>>>-marina
>>>
>>>Marina Vatkina wrote On 02/22/06 14:50,:
>>>
>>>
>>>
>>>
>>>>Hi Kedar,
>>>>
>>>>While, this is a good idea in general, I'm a bit confused on why
>>>>some options need no passwords and some need more than 1.
>>>>
>>>>You do not need a password at all to not only stop or start a domain
>>>>(why?), but to delete (!) a domain.
>>>>On the other hand to create a domain you need 2 passwords: admin and
>>>>master.
>>>>
>>>>To add to the above confusion, there is a password and an admin
>>>>password for the same [as_]admin command.
>>>>
>>>>My $.02.
>>>>
>>>>-marina
>>>>
>>>>Kedar Mhaswade wrote On 02/22/06 12:52,:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hi Marina,
>>>>> Good question, although this is not directly related to present
>>>>>change as passwordfile has always been there.
>>>>> The asadmin commands need several passwords and the way to specify
>>>>>those passwords is: AS_ADMIN_password-name. Since none of these can now
>>>>>be provided on the command line in clear, they have to be placed in file
>>>>>as name value pairs Following are the passwords:
>>>>>
>>>>>password intended contents of --passwordfile
>>>>>
>>>>>password => AS_ADMIN_PASSWORD=value
>>>>>adminpassword=>AS_ADMIN_ADMINPASSWORD=value (used only by create-domain
>>>>>command)
>>>>>master password=> AS_ADMIN_MASTERPASSWORD=value
>>>>>mq password => AS_ADMIN_MQPASSWORD=value
>>>>>
>>>>>And there are few others.
>>>>>
>>>>> We will improve the message as you suggested.
>>>>>
>>>>> Actually, all of this is moot once you use asadmin login command.
>>>>>I'd be interested in your feedback on this command. Once you
>>>>>successfully "login" [logical equivalent of the GUI's login screen] to a
>>>>>server (of course you'd need to start the server using asadmin
>>>>>start-domain command), you'd never need to supply any user name and
>>>>>passwords. Here is how the user experience changes (we hope this is a
>>>>>big plus!):
>>>>>
>>>>>BEFORE:
>>>>>place the password in passfile
>>>>>asadmin command-name-1 --user admin --passwordfile passfile ....
>>>>>asadmin command-name-2 --user admin --passwordfile passfile ....
>>>>>asadmin command-name-3 --user admin --passwordfile passfile ....
>>>>>asadmin command-name-4 --user admin --passwordfile passfile ....
>>>>>
>>>>>AFTER
>>>>>asadmin login
>>>>>asadmin command-name-1
>>>>>asadmin command-name-2
>>>>>asadmin command-name-3
>>>>>asadmin command-name-4
>>>>>
>>>>>....
>>>>>
>>>>>As the number of commands increase, the usability increases!
>>>>>
>>>>>
>>>>>Regards,
>>>>>Kedar
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>Marina Vatkina wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Kedar,
>>>>>>
>>>>>>Out of all this information, I can't find how my password file
>>>>>>should look like. I get the following (not helpful) error message:
>>>>>>
>>>>>>...Passwordfile should contain the following format AS_ADMIN_<password
>>>>>>option>=<password value>.
>>>>>>
>>>>>>What is <password option>?
>>>>>>
>>>>>>thanks,
>>>>>>-marina
>>>>>>
>>>>>>Kedar Mhaswade wrote On 02/16/06 17:31,:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>This is II reminder. The Saturday (18 Feb 2006) Build for GlassFish will
>>>>>>>have the changes that will reject any password that was provided on
>>>>>>>command line in clear.
>>>>>>>
>>>>>>>If you are used to the promoted GlassFish builds from
>>>>>>>glassfish.dev.java.net, promoted build b38 will have these changes.
>>>>>>>
>>>>>>>Let me know if you see any problems.
>>>>>>>
>>>>>>>Regards,
>>>>>>>Kedar
>>>>>>>
>>>>>>>
>>>>>>>Kedar Mhaswade wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hello All,
>>>>>>>>This is to let you know that we are doing a fundamental change to
>>>>>>>>the GlassFish admin CLI (aka asadmin) and that is to remove the
>>>>>>>>support the (so called) reusable passwords on command invocations.
>>>>>>>>Thus, --password on any remote asadmin command will not be supported.
>>>>>>>>
>>>>>>>>Following links have details:
>>>>>>>>
>>>>>>>>- The project page --
>>>>>>>>https://glassfish.dev.java.net/javaee5/admin-infra/subprojects/asadminlogin/index.html
>>>>>>>>
>>>>>>>>- The issue # 212 --
>>>>>>>>https://glassfish.dev.java.net/issues/show_bug.cgi?id=212
>>>>>>>>
>>>>>>>>Please start modifying your automated scripts if any, using
>>>>>>>>--passwordfile. If you can wait, please see if the new feature
>>>>>>>>"asadmin login" is useful to you (we believe so) in which case, the
>>>>>>>>remote commands may require neither --passwordfile nor will you be
>>>>>>>>prompted for the admin password.
>>>>>>>>
>>>>>>>>Let me know if you have any issues. And yes, spread the word.
>>>>>>>>
>>>>>>>>It looks like February 15, 2006 is when --password, --adminpassword
>>>>>>>>followed by their cleartext values will generate an error. If there is
>>>>>>>>any change in the plan, I will let you know in advance.
>>>>>>>>
>>>>>>>>Regards,
>>>>>>>>Kedar
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>---------------------------------------------------------------------
>>>>>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>>
>>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>>
>>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>>
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>