dev@glassfish.java.net

Re: Where to put new admin security-related commands

From: Tim Quinn <tim.quinn_at_oracle.com>
Date: Fri, 13 Aug 2010 11:26:09 -0500

On Aug 13, 2010, at 11:17 AM, Tom Mueller wrote:

> Tim,
> How about admin/cli-optional. This is where change-master-password
> is.

I don't know what determines the "optional-ness" of the commands in
admin/cli-optional but given what other commands are there that does
look like a better fit for enable-secure-admin and disable-secure-admin.

Thanks.

- Tim

>
> Tom
>
> On 8/13/2010 11:06 AM, Tim Quinn wrote:
>> Implementing the secure admin feature involves adding two new
>> commands, enable-secure-admin and disable-secure-admin.
>>
>> These will be used primarily in domains with instances which would
>> suggest they belong in cluster/cli - which are actually instance
>> related commands not commands related only to clusters, but that's
>> a separate topic entirely.
>>
>> It's possible, though, that a user running a domain containing only
>> the DAS would want to have the DAS authenticate itself to clients
>> using its certificate. So enabling secure admin would make sense
>> there too.
>>
>> So I am leaning toward putting these commands into admin/cli.
>>
>> Comments?
>>
>> - Tim
>>
>> ---------------------------------------------------------------------
>> 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
>