db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Created: (DERBY-2757) Do not require authentication when bringing up a security manager for the network server
Date Mon, 04 Jun 2007 20:03:26 GMT
Do not require authentication when bringing up a security manager for the network server
----------------------------------------------------------------------------------------

                 Key: DERBY-2757
                 URL: https://issues.apache.org/jira/browse/DERBY-2757
             Project: Derby
          Issue Type: Improvement
          Components: Network Server, Security
    Affects Versions: 10.3.0.0
            Reporter: Rick Hillegas
            Priority: Blocker
             Fix For: 10.3.0.0


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message