You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <de...@db.apache.org> on 2006/07/17 19:14:13 UTC
[jira] Created: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
----------------------------------------------------------------------------------------------------
Key: DERBY-1522
URL: http://issues.apache.org/jira/browse/DERBY-1522
Project: Derby
Issue Type: Task
Components: JDBC
Affects Versions: 10.2.0.0
Reporter: Mamta A. Satoor
Fix For: 10.2.0.0
There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Daniel John Debrunner updated DERBY-1522:
-----------------------------------------
Component/s: Test
(was: JDBC)
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Mike Matrigali updated DERBY-1522:
----------------------------------
Affects Version/s: 10.3.0.0
I ran full set of tests against ibm14.2, committed test only change to trunk.
m3_142:222>svn commit
Adding java\testing\org\apache\derbyTesting\functionTests\tests\lang\SQLAuthorizationPropTest.java
Sending java\testing\org\apache\derbyTesting\functionTests\tests\lang\_Suite.java
Sending java\testing\org\apache\derbyTesting\functionTests\util\SQLStateConstants.java
Sending java\testing\org\apache\derbyTesting\junit\DatabasePropertyTestSetup.java
Transmitting file data ....
Committed revision 441584.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh updated DERBY-1522:
--------------------------------
Derby Info: [Patch Available]
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433478 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
Thanks Mike for committing the patch. I would like this patch to be merged to 10.2. Merge command:
svn merge -r 441583:441584 https://svn.apache.org/repos/asf/db/derby/code/trunk
I tried the merge and ran the new test successfully in 10.2 branch. Can a committer please merge this change to 10.2?
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424703 ]
Mamta A. Satoor commented on DERBY-1522:
----------------------------------------
Deepa, you are right about testing the switch for both of following cases
1)As part of pre-10.2 db upgrade
2)A database created in 10.2 w/o SQL Standard Authorization gets switched to SQL Standard Authorization
I haven't given much thought to what kind of testing is involved. One thing that comes to my mind though is after the upgrade, all the existing schemas and objects in them should be owned by the dba and any other users will need to have permissions granted to them by the dba. Also, right after the upgrade, there should be nothing in the permissions related system tables because dba owns everything and no permissions has been granted to anyone yet. Similarly, the dependency manager should not have any permission related dependencies because dba does not need any permissions. Currently, dependency manager uses SYSDEPENDS table to keep track of permissions required for various objects. So, a check of SYSDEPENDS for permission dependencies will be a good idea in the tests right after the upgrade.
If anyone thinks of any other tests that we should be writing, please add them to this Jira entry.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Rick Hillegas updated DERBY-1522:
---------------------------------
Urgency: Normal
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424701 ]
Mamta A. Satoor commented on DERBY-1522:
----------------------------------------
I filed this jira entry to make sure that we test the switching and make sure everything works fine. Satheesh, you probably already added the test when you wrote the switching code but I was not sure and hence thought this jira entry would a good place holder for that task.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433152 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
Thanks Dan for the suggestions.
To try this, I used TestUtil methods for now. I'll open a Jira for adding shutdown methods in JUnit classes. I am able to run a particular test method with a specific setup. I think we need a small change in DatabasePropertyTestSetup.tearDown method where it tries to reset the properties to null. This gives an exception for 'derby.database.sqlAuthorization' property. Setting to null may not be supported for all properties.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433396 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
derbyall passed with 'derby1522_v2.diff' patch using Sun jdk 1.4.2 on Windows XP. Please review/commit this patch. Thanks.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425295 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
Thanks for the clarification, Mamta. I'll take a look at DERBY-1544.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh updated DERBY-1522:
--------------------------------
Attachment: derby1522_v2.diff
derby1522_v2.status
Attaching a patch 'derby1522_v2.diff. It includes a JUnit test for testing the switch to SQL standard authorization. It tests following:
1. grant/revoke is not available if derby.database.sqlAuthorization property is not set.
2. grant/revoke is available when derby.database.sqlAuthorization is set to true.
3. Once derby.database.sqlAuthorization is set to true, it cannot be set to any other value.
This patch also modifies DatabasePropertyTestSetup.tearDown method. The tearDown method resets the property values to old values. It will now ignore exceptions when property reset is not supported. I am including this small change in the above patch. (I had opened DERBY-1827 for the issue with tearDown method. ). I am using TestUtil.getConnection method to shutdown the database. I have opened DERBY-1826 to add methods to Derby's JUnit classes for shutdown.
Since the new test internally sets derby.database.sqlAuthorization property which cannot be reset, it may cause problems in tests which share the same database and rely on the value of this property. I am checking it does not affect any current tests by running derbyall. I have successfully run the new JUnit test standalone and as part of harness using Sun JDK 1.4.2 on Windows XP. Please take a look at this patch and provide feedback.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424694 ]
Satheesh Bandaram commented on DERBY-1522:
------------------------------------------
I was looking through all GRANT/REVOKE sub-tasks and related bugs. I am not sure exactly what this entry was filed to address.
Derby already supports switching from Derby authorization mode to SQL authorization mode. I think some of Deepa's tests already test this, though her changes are not committed yet. Not sure how much coverage those tests provide.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Satheesh Bandaram (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425338 ]
Satheesh Bandaram commented on DERBY-1522:
------------------------------------------
1) Mamta says: "after the upgrade, all the existing schemas and objects in them should be owned by the dba and any other users will need to have permissions granted to them by the dba."
Don't think that is true... Even in Derby authorization mode, schemas created by regular users have their authorizationId recorded in sysschemas. Derby authorization mode only recognises fullAccessUsers (who can modify any object owned by anyone) or readOnlyAccess or no access. But once switching to SQL authorization mode, only schema owners would have access to objects in their schema and others would need explicit GRANT from schema owner to be able to access them.
As far as additional testing for switching from Derby authorization mode to SQL mode, tests to cover include new restrictions we currently have on SQL authorization mode and to make sure they are actually enforced correctly. Some of the items to check, after switching to SQL authorization mode, include 1) Only owners can access their objects 2) regular users can only create a schema that matches their authorizationId 3) Database owner can access any object in the system 4) definer model being correctly enforced etc. 5) Access to many system routines are restricted 6) Cann't switch mode back to Derby authorization
Thanks Deepa for looking at DERBY-1544.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Mamta A. Satoor (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425289 ]
Mamta A. Satoor commented on DERBY-1522:
----------------------------------------
Deepa, to be more precise, in my statement
"after the upgrade, all the existing schemas and objects in them should be owned by the dba and any other users will need to have permissions granted to them by the dba." , the *dba* is the user who is attempting the upgrade. So, the correct behavior should be what DERBY-1544 is proposing to do.
I think DERBY-1544 should go into 10.2 but I am not sure if anyone is looking into it.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh updated DERBY-1522:
--------------------------------
Attachment: d1522_junit_v1.diff
d1522_junit_v1.status
I was trying to write a JUnit test case for this issue. The attached patch 'd1522_junit_v1.diff' (which is not for commit) covers the first part of the test. It is a small JUnit test which just checks grant/revoke is not available when sql authorization property is not set.
Next, I would like to set this property to true and then check grant/revoke is supported. I see that DatabasePropertyTestSetup has some methods to set database properties. I tried this but for the sql authorization property to take effect, we would need to shutdown and reconnect to the database. Shutdown can be done using existing TestUtil method but I wanted to check if there is something for this in JUnit helper classes. Also, is it possible to use DatabasePropertyTestSetup to set a property only for a particular test method?
This is my first attempt in writing a JUnit test and would appreciate help in how to proceed with this.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh reassigned DERBY-1522:
-----------------------------------
Assignee: Deepa Remesh
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12425269 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
Thanks Mamta for sharing your thoughts on this.
Reading this and the comments in DERBY-1544, I am confused and wondering what the planned behaviour for 10.2 is regarding the following:
1) Mamta says: "after the upgrade, all the existing schemas and objects in them should be owned by the dba and any other users will need to have permissions granted to them by the dba."
Current behaviour is what Mamta says. But DERBY-1544 is open to change the behaviour as follows:
"Upgrading a database from 10.1 to 10.2 should automatically change database owner, recorded as owner of system schemas in sysschemas, from pseudo user 'DBA' to authorizationID of the user attempting upgrade."
This is same as what the spec says.
2) DERBY-1544 mentions adding 5 system routines to routine permission table after a full upgrade.
Is DERBY-1544 planned for 10.2 or are we planning to keep the current behaviour?
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12427361 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
I had briefly looked at this task as I was working on DERBY-1521. I think we can cover the testing suggested by doing the following:
1) Create a database without setting derby.database.sqlAuthorization system property.
2) Test that grant/revoke statements are not supported
3) Set derby.database.sqlAuthorization (as a database property) to true. Shutdown and reconnect to database.
4) Test grant/revoke works by running lang/grantRevokeDDL.sql. This test seems to cover all the scenarios suggested.
5) Set derby.database.sqlAuthorization (as a database property) to false. Shutdown and reconnect to database.
6) Test that grant/revoke still works.
To me. only step 4 (running the existing test) seems to be a bit involved. Dan has suggested few options for this in DERBY-1521. Just posting this in case someone is planning to get to it soon.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh resolved DERBY-1522.
---------------------------------
Resolution: Fixed
Verified the fix for this issue is in trunk and 10.2. Thanks Mike and Rick for the commits.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0, 10.3.0.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Rick Hillegas updated DERBY-1522:
---------------------------------
Urgency: Urgent (was: Normal)
Bumping the urgency of this issue.
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.1.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12433121 ]
Daniel John Debrunner commented on DERBY-1522:
----------------------------------------------
The TestUtil class will not correctly report the "framework" when a JUnit test is run standalone. It would be great to have
some shutdown database and shutdown server method in the junit classes that works from TestConfiguration. I assume
that its location would be in TestConfiguration to match the openConnection() methods there.
For the second issue I think you can do something like this, if you had a test fixture method called "grantTestAfterChange"
public static Suite suite() {
// Adds all methodsthat start with 'test 'as test fixtures
TestSuite suite = new TestSuite(MyClass.class);
suite.addTest(new DatabasePropertyTestSetup (new MyClass("grantTestAfterChange", props));
}
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=all ]
Deepa Remesh updated DERBY-1522:
--------------------------------
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.2.1.0, 10.3.0.0
> Reporter: Mamta A. Satoor
> Assigned To: Deepa Remesh
> Fix For: 10.2.1.0, 10.3.0.0
>
> Attachments: d1522_junit_v1.diff, d1522_junit_v1.status, derby1522_v2.diff, derby1522_v2.status
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1522) Switch(if supported) from Derby
Authorization to Derby SQL Standard Authorization needs to be tested
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1522?page=comments#action_12424696 ]
Deepa Remesh commented on DERBY-1522:
-------------------------------------
I am covering a part of this in upgrade testing. I have a patch attached to DERBY-1521 which is pending review. In this patch, I have added a test to check that an upgraded database will support basic grant/revoke after switching to Derby SQL standard authorization. I am planning to add some more grant/revoke tests to be run after upgrade.
However, I am wondering if we should also test this switch for databases created in 10.2 itself. I mean test that a database created in 10.2 without SQL standard authorization can be switched to SQL standard authorization. Maybe, the code paths are not different for the switch of an upgraded database and a 10.2 database ? In that case, we may not need this test.
It would also be good to know what kind of test coverage is expected to test the "switch".
> Switch(if supported) from Derby Authorization to Derby SQL Standard Authorization needs to be tested
> ----------------------------------------------------------------------------------------------------
>
> Key: DERBY-1522
> URL: http://issues.apache.org/jira/browse/DERBY-1522
> Project: Derby
> Issue Type: Task
> Components: JDBC
> Affects Versions: 10.2.0.0
> Reporter: Mamta A. Satoor
> Fix For: 10.2.0.0
>
>
> There has been discussions on the Derby-dev list about switch from Derby Authorization to Derby SQL Standard Authorization for existing databases. If we do decide to support a switch like that, testing needs to be done/added to make sure everything works fine after the switch.
> ps I have added this JIRA entry to JDBC component but I am not 100% sure if that is the right component.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira