USER-DEFINED CLASS FOR AUTHENTICATION

["Petrula, Dan" <DP...@thezenith.com>]

Has anyone successfully implemented their own class to authenticate a
user's credentials?
I used as a format the sample class provided by Derby to do this.  But
there is scant information on the
particulars on how to do this.  I substituted my own class name for the
term 'BUILTIN' in the derby.properties file.
 
For some reason Derby is not loading the class.  Does one eliminate all
the text below the term '#Users' ?  Where does
this user class get placed in the directory structure?  I put it in two
places: in the same directory as the 'derby.properties' file and
in the directory where the server is started. It does not appear that
quotation marks (single or double) are placed around the
class name in the derby.properties file. The parameters in the
'getConnection()' method I left unchanged.
 
Any suggestions would be helpful.  I have been through all the
documentation and have not found the answers to these questions.
The server is running RH Linux.
 
Thanks
 
Dan

***********************************************************
NOTICE:
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 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
attached documents.

***********************************************************

Re: USER-DEFINED CLASS FOR AUTHENTICATION

[Francois Orsini <fr...@gmail.com>]

Hi Dan,

Did you set derby.authentication.provider to the *full name* of a class that
implements the public interface
org.apache.derby.authentication.UserAuthenticator? full name which includes
the various package names, etc.

The user-defined authentication class that implements
org.apache.derby.authentication.UserAuthenticator needs to be in the Java
classpath. Have you noticed any message(s) / exception(s) in derby.log file?

Cheers,

--Francois

On Thu, Dec 10, 2009 at 11:46 AM, Petrula, Dan <DP...@thezenith.com>wrote:

>  Has anyone successfully implemented their own class to authenticate a
> user's credentials?
> I used as a format the sample class provided by Derby to do this.  But
> there is scant information on the
> particulars on how to do this.  I substituted my own class name for the
> term 'BUILTIN' in the derby.properties file.
>
> For some reason Derby is not loading the class.  Does one eliminate all the
> text below the term '#Users' ?  Where does
> this user class get placed in the directory structure?  I put it in two
> places: in the same directory as the 'derby.properties' file and
> in the directory where the server is started. It does not appear that
> quotation marks (single or double) are placed around the
> class name in the derby.properties file. The parameters in the
> 'getConnection()' method I left unchanged.
>
> Any suggestions would be helpful.  I have been through all the
> documentation and have not found the answers to these questions.
> The server is running RH Linux.
>
> Thanks
>
> Dan
>
> ***********************************************************
> NOTICE:
> 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 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
> attached documents.
>
> ***********************************************************
>
>
>

Re: USER-DEFINED CLASS FOR AUTHENTICATION

[Rick Hillegas <Ri...@Sun.COM>]

Hi Dan,

The class just needs to be visible on the classpath.

Hope this helps,
-Rick

Petrula, Dan wrote:
> Has anyone successfully implemented their own class to authenticate a 
> user's credentials?
> I used as a format the sample class provided by Derby to do this.  But 
> there is scant information on the
> particulars on how to do this.  I substituted my own class name for 
> the term 'BUILTIN' in the derby.properties file.
>  
> For some reason Derby is not loading the class.  Does one eliminate 
> all the text below the term '#Users' ?  Where does
> this user class get placed in the directory structure?  I put it in 
> two places: in the same directory as the 'derby.properties' file and
> in the directory where the server is started. It does not appear that 
> quotation marks (single or double) are placed around the
> class name in the derby.properties file. The parameters in the 
> 'getConnection()' method I left unchanged.
>  
> Any suggestions would be helpful.  I have been through all the 
> documentation and have not found the answers to these questions.
> The server is running RH Linux.
>  
> Thanks
>  
> Dan
> ***********************************************************
> NOTICE:
> 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 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
> attached documents.
>
> ***********************************************************
>
>