Enable WebSphere ND "Test Connection" to Support Custom LoginModule via J2C-JAAS

Idea Summary:
Enhance the WebSphere ND administrative console's "Test Connection" function so that it leverages the same internal logic path used by application code, enabling support for custom credential retrieval mechanisms implemented via a custom LoginModule through the J2C-JAAS subsystem.

Detailed Description:
We have implemented our own credential retrieval via custom code into Websphere ND via a custom application login module implementing the LoginModule interface via the J2C-JAAS subsystem.

The module works:To use the custom module,  We change the Mapping Configuration Alias to use the custom module,  
set the enableContainerAuthForDirectLookups property on the connection pool 
and 
set the alias in the Container-managed authentication alias to the object we want to pass along to the module for subsequent retrieval.

This configuration works as expected when the data source is accessed by application code through JDBC.

However, when we click the “Test Connection" button in the console to test the data source, it IGNORES THE DATA SOURCE CONFIGURATION and reverts to using DefaultPrincipalMapping 

This behavior creates the following problems:
·        This is a problem for a LoginModule user because we can't use the in-built tools or scripting to validate the connection. 
·        The "Test Connection" button does authenticate with the database but is clearly using a different code path internally, as failure stack traces show it going through the driver and different internal code and ignores the custom module.
·        So, the only way to validate an application, in theory, is to hit the application code, which then triggers the module through whatever code path is provided in how an application accesses and interacts with the data source.

Workaround Identified:  
We have determined that if we retrieve the data source programmatically via JNDI, get a Connection from the DataSource object returned and call getConnection() on it, it will trigger the custom LoginModule. This allows one, through a custom application, to validate an arbitrary data source and prove it is using the custom code and is bypassing the local J2C-JAAS alias values

Proposed Enhancement:
Modify the internal logic of the "Test Connection" button to interact with JDBC in its test the same way applications do via the DataSource object.