If you write the tempfile into the config directory of the domain --
then you won't be breaking any rules.
On 4/28/2010 12:26 PM, Bobby Bissett wrote:
> Hi all,
>
> The upgrade tool prompts a user for a domain's master password, and
> then (if one is given) writes it to a temp file and passes it to
> asadmin with a --passwordfile option. As a reminder, the tool calls
> the command line interface of asadmin with a Runtime#exec call.
> Writing out this password in clear text is a no-no, so I need some
> other way to get the password into asadmin.
>
> It'd be great if we could drop the password from the tool completely,
> have the user do some form of 'asadmin login' first, and rely on the
> .asadminpass file that contains the hashed password, but I can only
> see that this applies to the admin password and not the master password.
>
> Does someone else have an idea of how I can handle this? Is there a
> way to avoid specifying the master password entirely when the
> --upgrade argument is present?
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188