[DERBY-5397] Make it possible to directly set a UserAuthenticator instance on the NetworkServerControl.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Network Server
• Labels: auth
• Assignee: Unassigned
• Reporter: Trejkaz
• Created: 31/Aug/11 01:29
• Updated: 03/Sep/11 22:51

Description

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