Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <97432918.178351263288774497.JavaMail.jira@brutus.apache.org>
Date: Tue, 12 Jan 2010 09:32:54 +0000 (UTC)
From: "Han Hong Fang (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
 with credentials to prevent unauthorized shutdowns
In-Reply-To: <2048027732.1221064304232.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Han Hong Fang updated GERONIMO-4296:
------------------------------------

    Attachment: G4296-Patch-branch-21.zip
                G4296-Patch-branch-22.zip

I create a patch for branch 22 (G4296-Patch-branch-22.zip).

I also notice that a new change required for branch 21, so I re-create the patch for branch 21 (G4296-Patch-branch-21.zip). Please ignore the previous attachments, and use the files in zip for branch 21.

Janet

> Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
> -----------------------------------------------------------------------------------
>
>                 Key: GERONIMO-4296
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4296
>             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
>
>         Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip, GERONIMO-4296-branch-21.patch, pom.xml
>
>
> Use the new NetworkServerControl support in Derby 10.4.1.3 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 -
> http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585
> 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.