| Summary: | Enablement implementations of IConnectionFactory.createConnection(IConnectionProfile profile, String uid, String pwd) disregard uid and pwd. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] Data Tools | Reporter: | jdoyleoss | ||||||
| Component: | Enablement | Assignee: | Brian Fitzpatrick <bfitzpat> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | ||||||||
| Version: | 1.8.1 | ||||||||
| Target Milestone: | 1.9 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
jdoyleoss
Created attachment 181746 [details]
How to reproduce
The easiest way I could think to give you a reproducible case is to use one of the plug-in wizards and hack the action. Do the following and you should be able to see how the Oracle impl just drops the username and password.
Import the attached project to your eclipse env with the DTP + DTP Enablement SDKs installed.
Change the values in the ctor for SampleAction.
Run the plugin in debug and run the SampleAction in the new Sample Menu that's added to the Main menu bar.
If you then change the username and password in the createDriverProps() call, you'll see it work.
This is more than just a tweak, but we should be able to still keep API backward compatibility when the fix goes in. The change affects everything down to the JDBCConnection/JDBCConnectionFactory level, so it will require changes to each of the enablement projects to correctly support the uid/pwd signature. I'm honestly not sure why this has never been seen until now - I'm guessing that the Teiid guys are just stressing the APIs in a different direction than we've seen in the past. Created attachment 181747 [details]
Patch for Connectivity & Oracle
This patch solves the problem for Oracle in my local tests, but will need to be tested further.
|