db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dev@xx" <...@proxiflex.fr>
Subject Re: Derby shutdown
Date Tue, 15 Sep 2009 13:28:20 GMT
thank you for this precision.

I have made more tests and have some more remarks.

I replace the BUILTIN provider by a UserAuthenticator implementation class.
I found that the example included in the documentation is not working if a system shutdown
is done.
In this case the authenticateUser method of the UserAuthenticator implementation is called
with null prameters (except info which has the "shutdown" property set). The example return
false if userName is null so system shutdown raise a "Connection authentication failure occurred."
exception.

If we do a system shutdown, it doesn't seam necessary to make database shutdown first (right
?), but do we need to make a system shutdown if we have previously made a database shutdown
?

JY Linet
  ----- Original Message ----- 
  From: Francois Orsini 
  To: Derby Discussion 
  Sent: Tuesday, September 15, 2009 1:01 AM
  Subject: Re: Derby shutdown


  Forgot to add that Yes, the documentation note should be fixed to mention that if authentication
has been enabled, then you do need to authenticate in order to shutdown a Derby system.

  Thanks


  On Mon, Sep 14, 2009 at 3:52 PM, Francois Orsini <francois.orsini@gmail.com> wrote:

    You have to set it _if_ you have defined Derby's BUILT-IN user authentication at the System
level (e.g. setting username / password in derby.properties file) versus having defined users
at the database level (e.g. database-level properties) - note that both types of users are
NOT exclusive, meaning you can have users defined at the system and database levels.

    http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevcsecure37817

    "Setting the property as a system-wide property creates system-wide users. Setting the
property as a database-wide property creates users for a single database only."

    See database-level properties versus system-level ones:
    http://db.apache.org/derby/docs/dev/devguide/devguide-single.html#cdevcsecure21547

    Hope this helps

    --francois



    On Mon, Sep 14, 2009 at 3:20 PM, dev@xx <dev@proxiflex.fr> wrote:

      Hi,
      The documentation says : << 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**.>>
      Even if authentication is enabled it doesn't seams that you have to set the user/password
attributes, only database shutdown needs these attributes.
      In fact I HAVE TO set the user/password attributes to shutdown the system or I have
a "Connection authentication failure occurred" exception.

      So my question is : is-it an error in the documentation or a bug or a misunderstanding
?

      Thanks,

      JY Linet




Mime
View raw message