db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-4377) Developer's Guide statement on shutting down Derby needs qualification
Date Tue, 29 Sep 2009 19:55:07 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase reopened DERBY-4377:
------------------------------


Reopening because we need to improve the revised statement:

Dag.Wanvik@Sun.COM (Dag H. Wanvik) writes:

> > "Francois Orsini (JIRA)" <jira@apache.org> writes:
> >
>> >> If you have enabled Derby's BUILTIN user authentication and created
>> >> some user at the system level (for example, by setting some username
>> >> and password in the derby.properties file), you will need to specify
>> >> credentials (e.g. username and password) in order to shut down a
>> >> Derby system.
> >
> > So if I understand this correctly; if users are defined only on the
> > database level (but BUILTIN user authentication is defined at the
> > system level), it will still be possible to shut down a Derby system
> > *without* supplying credentials?

Actually not. I tested this, and there needs to be defined at least
one user at the system level for a shutdown to work. So a more
precise wording would be:

"If you have enabled Derby's BUILTIN user authentication at the system
level (for example, by setting the property

      derby.connection.requireAuthentication=true 

in the derby.properties file), you will need to specify credentials
(e.g. username and password) in order to shut down a Derby system
*and* the supplied username/password must also be defined at the
system level."



> Developer's Guide statement on shutting down Derby needs qualification
> ----------------------------------------------------------------------
>
>                 Key: DERBY-4377
>                 URL: https://issues.apache.org/jira/browse/DERBY-4377
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.5.3.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY-4377-2.diff, DERBY-4377-3.diff, DERBY-4377.diff, tdevdvlp40464.html,
tdevdvlp40464.html, tdevdvlp40464.html
>
>
> The topic "Shutting down Derby or an individual database" (http://db.apache.org/derby/docs/dev/devguide/tdevdvlp40464.html)
begins,
> "Applications in an embedded environment shut down the Derby system by specifying the
shutdown=true attribute in the connection URL. To shut down the system, you do not specify
a database name, and you must not specify any other attribute."
> This statement actually needs some qualification, because (according to Francois Orsini)
"if you have defined Derby's BUILT-IN user authentication at the System level (e.g. setting
username / password in derby.properties file)" you do need to specify a username and password
when you shut down the database.
> The topic needs to include this information. Further suggestions on the wording are welcome.

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