[
https://issues.apache.org/jira/browse/DERBY-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096482#comment-13096482
]
Dag H. Wanvik commented on DERBY-5397:
--------------------------------------
Could you show is in a little more detail what you believe the issue is? A
repro would be good..
> Make it possible to directly set a UserAuthenticator instance on the
> NetworkServerControl.
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-5397
> URL: https://issues.apache.org/jira/browse/DERBY-5397
> Project: Derby
> Issue Type: Improvement
> Components: Network Server
> Reporter: Trejkaz
> Labels: auth
>
> We are using NetworkServerControl to embed the Derby server. We would like
> to use our own user authenticator for this. Currently, this requires setting
> a system property and Derby creates a brand new instance every time it needs
> to call it.
> This wreaks havoc with our development philosophy because we would like to
> unit test our stuff, but Derby is constructing an instance directly instead
> of letting us pass a mock authenticator.
> The workaround we are using is:
> * Set the real authenticator as a static field somewhere and provide
> register()/deregister()/lookup() access methods
> * Make a DelegatingUserAuthenticator which calls lookup() on the real thing
> and then delegates the call to it
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
