Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
10.9.1.0
-
None
-
Normal
Description
If you connect to a db with native authentication using strong password substitution to protect the password, you'll get a protocol error:
ij(CONNECTION2)> connect 'jdbc:derby://localhost/db;user=app;password=papp;securityMechanism=8';
ERROR 08006: A network protocol error was encountered and the connection has been terminated: A PROTOCOL Data Stream Syntax Error was detected. Reason: 0x18. Plaintext connection attempt to an SSL enabled server?
I don't think strong password substitution is intended to work with NATIVE, but it should probably fail more gracefully. With BUILTIN, you'll get a more helpful error message:
ij(CONNECTION5)> connect 'jdbc:derby://localhost/db2;user=app;password=papp;securityMechanism=8';
ERROR 08004: DERBY SQL error: SQLCODE: -1, SQLSTATE: 08004, SQLERRMC: Connection authentication failure occurred. Either the supplied credentials were invalid, or the database uses a password encryption scheme not compatible with the strong password substitution security mechanism. If this error started after upgrade, refer to the release note for DERBY-4483 for options.
Attachments
Issue Links
- is related to
-
DERBY-6702 test failure in NSSecurityMechanismTest; The expected SQL state must be five characters long
- Closed
- relates to
-
DERBY-866 Derby User Management Enhancements
- Closed