geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Han Hong Fang (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
Date Tue, 15 Dec 2009 02:57:18 GMT


Han Hong Fang commented on GERONIMO-4296:

Username and password are not required to start the NetworkServerControl. 

To introduce user id and password checking when stop NetworkServerControl, we must enable
derby user authentication. And with user authetication enabled, no matter stopping NectworkServerControl
or accessing derby databases, user needs to provide user id and password, and then be authenticated
in a unified way.  

It covers both the stop issue described in this JIRA and access issue in this JIRA:

> Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
> -----------------------------------------------------------------------------------
>                 Key: GERONIMO-4296
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: databases
>    Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2
>            Reporter: Donald Woods
>            Assignee: Donald Woods
>            Priority: Minor
>             Fix For: Wish List
> Use the new NetworkServerControl support in Derby and later to start our embedded
Derby server with credentials, to prevent any other apps on localhost from stopping our Derby
instance.  The following Derby release note details the scenario and the new API -
> We could either use random uid/pwd values to start the Derby server, which would be the
most secure, but would keep other apps from using our Derby server.  The other option, would
be to set uid/pwd GBean attributes and default the to the default system/manager values and
leave it up to the user to change them.
> Note:  This may also require some Samples, Testsuite and Portlet chagnes to handle the
required DB auth.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message