[DERBY-5970] Check that connection attributes have legal values.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.10.1.1
• Component/s: Services
• Labels: derby_triage10_11
• Urgency: Normal
• Bug behavior facts: Security
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 29/Oct/12 19:46
• Updated: 18/Aug/14 14:36

Description

At boot time, Derby does not check whether connection attributes are set to legal values. This can cause them to be silently ignored. In the case of security operations like re(un)encryption, these silent failures deceive the DBO into thinking that the security behavior of the database has changed when, in fact, it hasn't. We should do the following:

1) Prevent decryptDatabase from being set to an illegal value. Since this is a new attribute, there are no backward compatibility issues.

2) Evaluate other attributes on a case-by-case basis to determine which ones should raise exceptions if they are set to illegal values. Technically, this may result in backwardly incompatible behavior. However, I think that for most attributes, we will decide that the incompatibility is minor and is a welcome bugfix.

Issue Links

• incorporates: DERBY-284 Show warning message , if hard upgrade was not executed because upgrade=true was designated on or after 2nd connection.
• incorporates: DERBY-4254 If upgrade is not performed when connecting with the upgrade=true atribute is specified, Derby should produce a warning
• is related to: DERBY-6706 Derby does not check invalid configuration option name in derby.properties
• is related to: DERBY-1151 ij does not issue a warning if the attribute verifyKey.dat is set on an embedded URL.
• is related to: DERBY-5993 The Reference Manual shows an embedded url in its example for the client-side-only retrieveMessageText attribute.
• is related to: DERBY-6002 Reference manual is unclear on when territory can be set
• relates to: DERBY-5907 Warnings missing on client driver
• relates to: DERBY-5792 Make it possible to turn off encryption on an already encrypted database.