network server boot fails indicating authentication must be set up even when authentication is fully defined in derby.properties

• Key: DERBY-2435
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Critical
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Component/s: Network Server
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4

Description

Booting the server using the default to install a security manager fails even when the derby.properties is in the current directory with these contents.

derby.connection.requireAuthentication=true
derby.authentication.provider=BUILTIN
derby.user.SA=sapwd
derby.user.MARY=marypwd

The documentation on authentication indicates this is the preferred way to setup authentication for a server machine.

Comments

[Rick Hillegas]

Attaching fix: derby-2435-01.diff. This patch does the following:

M java/drda/org/apache/derby/drda/NetworkServerControl.java

  Uses PropertyUtil to get the properties.

A java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/SecureServerTest.derby.properties

  This is the sample derby.properties which showed this bug. Used by a new test case.

M java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/SecureServerTest.java

  Adds new test case to bring up the server using the sample derby.properties which showed this bug.

M java/testing/org/apache/derbyTesting/junit/SupportFilesSetup.java

  Allows testing files to be copied to specific target file names. Supports copying of SecureServerTest.derby.properties to derby.properties.

[Rick Hillegas]

Committed derby-2435-01.diff at subversion revision 519004. Derbyall and the junit tests ran cleanly except for the DerbyNetClient run of checkDataSource30. That test failed beginning with this error:

*** Start: checkDataSource30 jdk1.4.2_12 DerbyNetClient derbynetmats:jdk14 2007-03-15 14:31:10 ***
293 del
< FAIL incorrect connection object returned for Statement.getConnection()
293a293,296
> FAIL incorrect connection object returneException in thread "main" org.apache.derby.client.am.XaException: XAER_NOTA : Error executing a XAResource.start(), server returned XAER_NOTA.
> Caused by: org.apache.derby.client.am.SqlException: Error executing a XAResource.start(), server returned XAER_NOTA.
> ... 4 more

I re-ran the test against the classtree and against the jar files and was unable to reproduce the failure. I think it is unlikely that my changes introduced this heisenbug into this test.

[Rick Hillegas]

Unassigning. I believe this issue can be closed.