[DERBY-2757] Do not require authentication when bringing up a security manager for the network server

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Network Server
• Issue & fix info: Release Note Needed
• Bug behavior facts: Security
• Assignee: Richard N. Hillegas
• Reporter: Richard N. Hillegas
• Created: 04/Jun/07 20:02
• Updated: 30/Jun/09 00:14
• Resolved: 06/Jun/07 20:24

Description

DERBY-2196 brings up a security manager-if the user forgot to install one-when the network server is booted. DERBY-2196 requires that authentication be enabled when bringing up a security manager. If authentication is not enabled, then the server fails to boot and, instead, prints out a diagnostic advising the user to enable authentication, and, if that is not possible, boot the server with the -noSecurityManager option.

This creates an incompatibility for applications upgrading from previous Derby releases. Despite the advice in Derby user guides, customers do boot the network server without enabling authentication. This incompatibility is discussed in the email thread http://www.nabble.com/forum/Search.jtp?forum=105&local=y&query=SecurityManager+incompatibility

This JIRA removes the requirement that authentication be enabled when the server brings up a security manager.

Issue Links

• relates to: DERBY-2196 Run standalone network server with security manager by default