You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2008/09/10 18:31:44 UTC
[jira] Created: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
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: 2.2
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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791785#action_12791785 ]
Han Hong Fang commented on GERONIMO-4296:
-----------------------------------------
Here is the default derby user information.
User: dbadim
Password: manager
Group: derbyadmin
This user is used by Geronimo modules when operating with Derby. The user name and group name of default derby user can NOT be changed, but the default password can with following steps.
1. Start Geronimo server
2. Change password of dbadmin in console >security > Users and Groups portlet
3. Change the user password in existing datasources in console > Services > Database pools portlet
4. Shutdown Geronimo server
5. Change the userPassword attribute of DerbyNetwork GBean in var\config\config.xml
6. Restart Geronimo server
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929582#action_12929582 ]
Kevan Miller commented on GERONIMO-4296:
----------------------------------------
Shouldn't this be fixed in trunk, also?
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.7, 2.2.1
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang updated GERONIMO-4296:
------------------------------------
Attachment: (was: pom.xml)
> 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
>
>
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799132#action_12799132 ]
Han Hong Fang commented on GERONIMO-4296:
-----------------------------------------
I deleted the previous attachments to avoid confusion.
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
>
>
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang updated GERONIMO-4296:
------------------------------------
Attachment: (was: GERONIMO-4296-branch-21.patch)
> 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
>
>
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire updated GERONIMO-4296:
-----------------------------------
Fix Version/s: 2.1.7
(was: 2.1.6)
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.7, 2.2.2
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790544#action_12790544 ]
Donald Woods commented on GERONIMO-4296:
----------------------------------------
OK, so if 4878 is implemented, then it should also cover this issue.
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-4296:
-----------------------------------
Assignee: (was: Donald Woods)
> 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
> Priority: Minor
> Fix For: Wish List
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang updated GERONIMO-4296:
------------------------------------
Attachment: pom.xml
GERONIMO-4296-branch-21.patch
The patch for branch 2.1 is ready, please help to review and follow the steps below to commit it.
1. apply patch GERONIMO-4296-branch-xy.patch
2. create folder plugins\derby\derby
3. move all files under plugins\derby\ to plugin\derby\derby
4. add pom.xml into plugins\derby\
5. move plugins\system-database\geronimo-derby to plugins\derby\geronimo-derby
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: 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-4296:
-----------------------------------
Fix Version/s: (was: 2.2)
Wish List
Good idea but lacks implementation
> 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.
[jira] Assigned: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan reassigned GERONIMO-4296:
------------------------------
Assignee: Ivan
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.6, 2.2.1
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929515#action_12929515 ]
Forrest Xia commented on GERONIMO-4296:
---------------------------------------
Verify the patch on G 2.1.7 snapshot, and commit it to 2.1 branch at rev 1032500.
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.7, 2.2.2
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790535#action_12790535 ]
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: https://issues.apache.org/jira/browse/GERONIMO-4878
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Radim Kolar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758838#action_12758838 ]
Radim Kolar commented on GERONIMO-4296:
---------------------------------------
I see this as quite serious security problem. If this issue will not be fixed before 2.2, it should be visibly noted in README that people should firewall derby listener from untrusted clients. Same thing is for ActiveMQ broker.
correct thing for derby is to write derby.authentication.provider module and connect it to user specified G security realm configurable via console portlet.
Derby side is pretty simple: derby.authentication.provider class must implement the public interface org.apache.derby.authentication.UserAuthenticator and throw exceptions of the type java.sql.SQLException where appropriate.
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4296:
----------------------------------
Fix Version/s: 2.2.2
(was: 2.2.1)
won't fix this in 221 release.
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.6, 2.2.2
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12929899#action_12929899 ]
Forrest Xia commented on GERONIMO-4296:
---------------------------------------
Open GERONIMO-5678 for trunk fix track.
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.7, 2.2.1
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Radim Kolar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833747#action_12833747 ]
Radim Kolar commented on GERONIMO-4296:
---------------------------------------
Will this patch ship in 2.2.1?
> 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
> Priority: Minor
> Fix For: Wish List
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Jack Cai (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790060#action_12790060 ]
Jack Cai commented on GERONIMO-4296:
------------------------------------
I think it makes sense to use the geronimo-admin realm, as the embedded Derby is not for production use of other purpose.
> 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.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4296:
----------------------------------
Fix Version/s: 2.1.6
2.2.1
(was: Wish List)
> 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
> Priority: Minor
> Fix For: 2.1.6, 2.2.1
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.
[jira] Commented: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790029#action_12790029 ]
Han Hong Fang commented on GERONIMO-4296:
-----------------------------------------
I did a quick research on this topic, and propose a solution for tihs issue as below.
1. enable user authentication in our embedded Derby server
2. use user-defined class as derby.authentication.provider. The user-defined class should implements derby required public interface org.apache.derby.authentication.UserAuthenticator
3. use Geronimo security realm (using the default realm named geronimo-admin) to store the derby user ids and passwords. Set default user id/pwd in geronimo-admin as dbadmin/manager, and put it into a new group name such as derbyGroup. The information will be used in the implementation of user-defined UserAuthenticator
4. set the default derby user id/pwd (i.e., dbadim/manager) into the deployment plan of existing datasources (e.g., SystemDatabase) to make sure they works after enabling user authentication in our embedded Derby server.
5. Geronimo user has the chance to modify derby user id/pwd by modifying the property file behind geronimo-admin security realm, but he/she is required to edit the datasources and var\config\config.xml if the default derby use rid/pwd is changed.
I have a question related item 3, shall user in console admin group (e.g., system/manager) be used to log in our derby?
Your comments is also highly appreciated.
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
>
>
> 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.
[jira] Closed: (GERONIMO-4296) Start Derby NetworkServerControl
with credentials to prevent unauthorized shutdowns
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Forrest Xia closed GERONIMO-4296.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.2.2)
2.2.1
Commit to 2.2 branch at rev 1032508. So close it for now. If any bug related, pls open a new jira against the proper server version.
> 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: Ivan
> Priority: Minor
> Fix For: 2.1.7, 2.2.1
>
> Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip
>
>
> 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.