db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyTenThreeRelease" by RichardHillegas
Date Thu, 22 Feb 2007 16:22:27 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by RichardHillegas:
http://wiki.apache.org/db-derby/DerbyTenThreeRelease

------------------------------------------------------------------------------
  == 10.3 Big Features ==
  
  || Feature || Description || Associated JIRAs ||
- || System Privileges || Control who can shutdown the engine and who can create databases.
|| Master JIRA: [https://issues.apache.org/jira/browse/DERBY-2109 DERBY-2109] ||
  || DBA Powers || Control who can shutdown, encrypt and upgrade databases. || Master JIRA:
[https://issues.apache.org/jira/browse/DERBY-2264 DERBY-2264] ||
  || Secure Server || Make the Network Server secure by default. || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-2196
DERBY-2196] ||
  || Language Based Ordering || Add built in language based ordering and like processing to
Derby. || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-1478 DERBY-1478] ||
@@ -53, +52 @@

  
  [http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12311517
Open 10.3 documentation issues]
  
+ == Incompatibilities Upgrading from 10.2 ==
+ 
+ The Secure Server work ([https://issues.apache.org/jira/browse/DERBY-2196 DERBY-2196]) introduces
the following incompatibility during upgrade from release 10.2:
+ 
+ || '''Scenario''' || '''Old behavior''' || '''New behavior''' || '''Customer needs to make
these changes...''' ||
+ ||  '''Unsecure but Authorized'''|| In this scenario, !NetworkServerControl is the main
entry point for the VM and the VM starts up without a !SecurityManager. However, the customer
has turned on user authentication|| The server comes up as before. However, under the hood,
 !NetworkServerControl installs a !SecurityManager. Among      other side-effects, this may
affect the running of      customer-written procedures and functions. The customer may need
to instrument her code to run under a !SecurityManager.|| Probably the customer does not need
to do anything. However, the customer may need to bring the server up with the -noSecurityManager
flag if the !SecurityManager causes her  problems--for instance, if she does not want to instrument
the rest of her application to work under a !SecurityManager.||
+ ||  '''Unsecure and Unauthorized'''|| In this scenario, !NetworkServerControl is the main
entry point for the VM and the VM starts up without a !SecurityManager. In addition, there
is no user authentication.|| The server fails to come up because user authentication is not
turned on.|| The customer must either turn on user authentication or bring the server up with
the -noSecurityManager flag. ||
+ 
+ 
+ The DBA Powers work ([https://issues.apache.org/jira/browse/DERBY-2264 DERBY-2264]) introduces
the following incompatibility during upgrade from release 10.2:
+ 
+ ||  '''Privilege'''|| '''Previous behavior...'''|| '''Behavior after these changes...'''||
'''Impacts...'''|| '''How to upgrade application...'''||
+ ||  '''shutdown database'''|| Anyone who could connect could shutdown a database.|| A database
can be shutdown only by  its owner.|| All applications.|| Anyone who must shutdown the database
must connect as the Database Owner.||
+ ||  '''upgrade database'''|| Anyone who could connect could upgrade the database.|| Only
the Database Owner can upgrade the database.|| All applications.|| Anyone who must upgrade
the database must connect as the Database Owner.||
+ ||  '''encrypt database'''|| Anyone who could connect could encrypt the database.|| Only
the Database Owner can encrypt or re-encrypt the database.|| All applications.|| Anyone who
must encrypt the database must connect as the Database Owner.||
+ 

Mime
View raw message