| Bug #82478 | jdbc: lack of login-path usage | ||
|---|---|---|---|
| Submitted: | 5 Aug 2016 20:27 | Modified: | 9 Aug 2016 12:12 |
| Reporter: | Jacek Machura | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | Connector / J | Severity: | S4 (Feature request) |
| Version: | 5.1.39 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | encryption, jdbc, password | ||
[9 Aug 2016 12:12]
Chiranjeevi Battula
Hello Jacek Machura, Thank you for the bug report. Verified based on internal discussion with dev's will take it up as a feature request. Thanks, Chiranjeevi.
Description: Can't find "login-path" parameter to be used in jdbc connection to take advantage of native encrypted password in mysql 5.6.6 and above. mysql Perl Client can easily connect using only "login-path", no open password required! How to repeat: I didn't find way to replace user/password with "login-path" : conn = DriverManager.getConnection("jdbc:mysql://localhost/test?" + "user=minty&password=greatsqldb"); Suggested fix: conn = DriverManager.getConnection("jdbc:mysql://localhost/test?" + "login-path=myLoginPath");