db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Kutty (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2433) Error message when booting server with no authentication is misleading
Date Thu, 17 May 2007 23:41:16 GMT

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

Manjula Kutty commented on DERBY-2433:

I bumped in to a similar problem while running the scripts from the bin directory. The Message
is misleading. Also the scripts should either start the server with -noSecurityManager option
or should have a proper error message like the one for the DERBY_HOME  to set the authentication
properties or as a third option can give generic authentication properties in default derby.properties

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

View raw message