You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2007/05/29 22:49:16 UTC
[jira] Assigned: (DERBY-2433) Error message when booting server
with no authentication is misleading
[ https://issues.apache.org/jira/browse/DERBY-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas reassigned DERBY-2433:
------------------------------------
Assignee: Rick Hillegas
> 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
> Assignee: Rick Hillegas
>
> 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.