dev@glassfish.java.net

Re: Where to put new admin security-related commands

From: Byron Nevins <byron.nevins_at_oracle.com>
Date: Fri, 13 Aug 2010 09:29:39 -0700

cli-optional is a packaging phenomenon. It was added as a way of toning
down the size of admin/cli and to cut back on dependencies.

On 8/13/2010 9:26 AM, Byron Nevins wrote:
> The clustering jars can completely disappear in cases where there is
> no need for "clustering" support. Don't put them in the cluster
> source area if they need to always be available...
>
>
> On 8/13/2010 9: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
>>
>

-- 
Byron Nevins  -  Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188