[jbossts-issues] [JBoss JIRA] (JBTM-3000) Support for Oracle Wallet JDBC connections

[Anonymous (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Issue was automatically transitioned when dshaver1 created pull request #1294 in GitHub
---------------------------------------------------------------------------------------
    Status: Pull Request Sent  (was: Open)


> Support for Oracle Wallet JDBC connections
> ------------------------------------------
>
>                 Key: JBTM-3000
>                 URL: https://issues.jboss.org/browse/JBTM-3000
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>            Reporter: Daniel Shaver
>            Priority: Optional
>
> In the latest snapshot build, Narayana will replace a null username and/or password with empty strings (""). The Oracle JDBC driver, however, supports passing in null username and password, in order to make use of Oracle Wallet.
> This means that Narayana does not support Oracle Wallet JDBC connections.
> This replacement is being done in com.arjuna.ats.internal.jdbc.ConnectionImple. 
> {code:java}
>             user = info.getProperty(TransactionalDriver.userName, "");
>             passwd = info.getProperty(TransactionalDriver.password, "");
> {code} 
> and in com.arjuna.ats.internal.jdbc.ConnectionManager
> {code:java}
>         String user = info.getProperty(TransactionalDriver.userName, "");
>         String passwd = info.getProperty(TransactionalDriver.password, "");
> {code}
> I believe it should be okay to just remove default value so that the client's input is always taken as-is.
> I was able to successfully build test this change out locally, using OJDBC 12.2.0.1 and Oracle UCP 12.2.0.1 running in a spring boot/tomcat container.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)