[QPID-3373] Java client: connectionFactory.createConnection method should not rewrite stored credentials

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.10
• Fix Version/s: 0.14
• Component/s: JMS AMQP 0-x
• Assignee: Rajith Muditha Attapattu
• Reporter: Pavel Moravec
• Created: 27/Jul/11 12:37
• Updated: 14/Mar/17 20:07
• Resolved: 31/Aug/11 00:26

Description

Method connectionFactory.createConnection("foo", "bar") causes than Java client caches the credentials and overwrites default ones provided in connection URL. Thus subsequent calling of connectionFactory.createConnection() method (without a parameter) results in using the credentials "foo" / "bar" despite default ones should be used.

How reproducible:
100%

Steps to Reproduce:
1. Setup a broker with PLAIN authentication
2. Compile attached JUnit test
3. Run it (java org.junit.runner.JUnitCore authNoCredentialsInSecondConnection)

Actual results:
In try .. catch block, connectionFactory2.createConnection(); does not raise an exception that authentication failed. (and thus fail command below raises java.lang.AssertionError exception). In fact, connectionFactory2.createConnection(); uses "guest" / "guest" credentials set for connectionFactory1.

Expected results:
Authentication fails for connectionFactory2.createConnection(); as it uses default credentials from URL (what is "dummy" / "dummy").