db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Petrula, Dan" <DPetr...@thezenith.com>
Subject Password Authentication Failure
Date Wed, 23 May 2007 17:08:35 GMT
I am using a client-server configuration with the datebase located on a
separate server. If I set 'derby.connection.requireAuthentication=true'
'derby.authentication.provider=BUILTIN' , and 'derby.user.dan=danpass'
in the derby.properties file, I get the error message
SQLException:Schema 'DAN'
does not exist. I am passing a Properties object containing the password
name/value pairs as an attribute to the connection url
I would like to set system-wide properties using the 'BUILTIN'
authenication provider. There are many examples in Derby documents
showing the
 passing of a Properties object or just string value pairs  combinations
to Derby.
However, I came upon a note on page 9 of "Tuning Derby" dated 12-11-06.
This notes says "If you pass in a Properties object as an argument to
DriverManager.getConnection call when connecting to the database, those
properties are used as a database connection URL attribute, not as
of the type discussed in this book".
I am not sure how to interpret that statement. However, it seems to
imply that:
    1. It is not possible to authenticate using system-wide properties
by passing a password name/value pair as an attribute.
    2. The only way to validate by passing an attribute seems to be at
the database level.
    3. I am assuming the use of the 'BUILTIN' authentication provider.
If I create the database using user=dan & password=danpass during the
creation process, I can connect to the database by passing the
Properties object
and setting derby.connection.requireAuthentication=true. If I don't set
the authentication and don't pass the Properties object, I can connect
to the database.
If I am correct in my numbered statements, what is the purpose of the
'BUILTIN' option as an authentication provider using system-wide
properties? It does not
appear that it can be used.
Of course maybe I just don't understand this authentication process.
Anyone have any comments?

This e-mail, including attachments, contains information that may be  confidential,  protected
by the attorney/client or other privileges, or exempt from disclosure under applicable law.
Further, this e-mail may contain information that is proprietary and/or constitutes a trade
secret. This e-mail, including attachments, constitutes non-public information intended to
be conveyed only to the designated recipient(s). If you are not an intended recipient of this
communication, please be advised that any disclosure, dissemination, distribution, copying,
or other use of this communication or any attached document is strictly prohibited.  If you
have received this communication in error, please notify the sender immediately by reply e-mail
and promptly destroy all electronic and printed copies of this communication and any attached


View raw message