[GERONIMO-4296] Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.3, 2.1.3, 2.1.4, 2.2
• Fix Version/s: 2.1.7, 2.2.1
• Component/s: databases
• Security Level: public (Regular issues)
• Assignee: Haihong Xu
• Reporter: Donald Woods
• Created: 10/Sep/08 16:30
• Updated: 06/Dec/10 07:40
• Resolved: 08/Nov/10 09:47

Description

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.

Issue Links

• is related to: GERONIMO-5706 When derby authentication is disabled, DB manager portlet run SQL error: Caused by: java.sql.SQLException: Schema 'DBADMIN' does not exist
• relates to: GERONIMO-5723 derby system-database user authentication failure when shutdown server using sun jdk 1.6.0