[DERBY-2356] Make SSL server authentication optional

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Network Client, Network Server
• Bug behavior facts: Security
• Assignee: Bernt Johnsen
• Reporter: Bernt Johnsen
• Created: 19/Feb/07 14:21
• Updated: 30/Jun/09 00:14
• Resolved: 26/Feb/07 19:05

Description

Default SSL behaviour is to require serer authentication. For a database application this is not as important as it is for web browsers and also creates som extra hassle for the user/application programmer. Since the main objective for SSL in Derby is encryption on the wire, server authentication should be optional (the same way client authentication is).

This also creates some symmetry which can be exploited to simplify the user interfce somewhat. This improvement to DERBY-2108 is described in the attached functional specification. See the attachment for details.

Issue Links

• is related to: DERBY-2108 Implement SSL/TLS communication between client and server
• relates to: DERBY-2363 Add initial handshake on connection setup to determine server's required ssl support level and avoid client side attribute settings.