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] Commented: (DERBY-2433) Error message when booting server with no authentication is misleading
Date Fri, 18 May 2007 15:23:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496910
] 

Rick Hillegas commented on DERBY-2433:
--------------------------------------

How about this alternative text for the message: 

Network Server startup failed. User authentication must be enabled before the Network Server
installs a security manager. Please either enable user authentication or disable the installation
of a security manager. To enable user authentication, please consult the section of the Derby
Developer's Guide titled "Working with user authentication". Disabling the installation of
a security manager is highly discouraged in a client/server environment. However, if you must
do this, you can disable the installation of a security manager by specifying the '-noSecurityManager'
command line option when you bring up the Network Server.


> Error message when booting server with no authentication is misleading
> ----------------------------------------------------------------------
>
>                 Key: DERBY-2433
>                 URL: https://issues.apache.org/jira/browse/DERBY-2433
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.3.0.0
>            Reporter: Daniel John Debrunner
>
> jar -jar lib/derbyrun.jar server start
> Network Server startup failed. User authentication should be enabled before the
> Network Server installs a security manager. Please either set the 'derby.connect
> ion.requireAuthentication' system property to true or run the network server wit
> h the '-noSecurityManager' option.
> 1) Setting derby.connection.requireAuthentication to true is not sufficient to have a
working system.
> 2) Use of "should" in "should be enabled", it's a requirement, so use "must"
> 3) Hopefully setting the derby properties in derby.properties also works so there is
no requirement for the authentication to be defined using *system* properties.
>  Maybe the wording could just state that authentication must be setup and somehow reference
the appropriate properties?

-- 
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