I don't understand why password aliases would not be per-domain.
We recently reviewed the options for commands, maybe we missed this one?
Anissa Lam wrote on 11/02/2010 05:25 PM:
>
> In order to have better user experience on creating/editing Nodes in GUI, Joe
> requested me to allow user to specify password alias for the SSH Authentication,
> besides just allowing KeyFile.
> So I looked in Password Aliasing in 3.1, and notice a significant difference
> when compared to v2.
>
> In 2.1, it seems that password alias is per domain, there is no --target option.
> Usage: create-password-alias [--terse=false] [--echo=false] [--interactive=true]
> [--host localhost] [--port 4848|4849] [--secure | -s] [--user admin_user]
> [--passwordfile file_name] aliasname
>
> In 3.1, password alias takes in a target, and needs to be cluster/standalone
> instance/server
> Usage: asadmin [asadmin-utility-options] create-password-alias
> [--target <target(default:server)>] [-?|--help[=<help(default:false)>]]
> aliasname
> and it will not take "domain" as target.
>
> I want to know if this is by design or just an overlook. If it is by-design,
> then GUI will not be able to list out the password aliases for user to select
> when creating Node for SSH authentication, as Node creation is per domain.
>
> I also see a couple bugs when trying to create/list password alias. I will file
> issues on that.
>
> thanks
> Anissa.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>