[
https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790280#action_12790280
]
Donald Woods commented on GERONIMO-4296:
----------------------------------------
The new API I was referring to, allows you to supply a password when starting
the embedded server, which must be used to stop the server. This JIRA was not
meant to expose the system database with a credential store, but to simply
create a random password to pass in when starting Derby, store it in memory and
then use it to stop the server (simple scheme to prevent other apps inside or
outside the Geronimo JVM from killing our Derby instance and not a guarantee
since someone wit a debugger could find the key.) We don't need to share the
password with other apps or users, as it is only used to start/stop the
embedded Derby.....
> 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
>
>
> 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.
