Back to bug 728509

Who When What Removed Added
Pavel Moravec 2011-08-05 12:00:51 UTC Priority unspecified medium
Target Milestone --- 2.0.2
Pavel Moravec 2011-08-05 12:01:13 UTC Group private
Mike Cressman 2011-08-11 21:03:48 UTC CC mcressma
Target Milestone 2.0.2 2.0.3
Ted Ross 2011-08-22 19:47:38 UTC CC tross
Ted Ross 2011-08-22 19:51:22 UTC Target Milestone 2.0.3 ---
Irina Boverman 2011-09-09 18:12:53 UTC Target Milestone --- 2.1.1
Justin Ross 2011-11-10 21:05:21 UTC Status NEW ASSIGNED
CC jross
Assignee rhm-maint-list rattapat
Target Milestone 2.1.1 Next Version
Pavel Moravec 2012-08-13 14:03:32 UTC Keywords EasyFix, Patch
Link ID Apache JIRA QPID-3396
Pavel Moravec 2012-08-13 15:53:44 UTC Attachment #604019 Attachment is obsolete 0 1
Pavel Moravec 2012-08-17 11:58:31 UTC Attachment #604035 Attachment is obsolete 0 1
Pavel Moravec 2013-01-14 11:58:53 UTC Keywords TestCaseProvided
Justin Ross 2013-02-22 13:48:35 UTC Target Milestone Next Version 2.4
Leonid Zhaldybin 2013-02-26 08:09:59 UTC CC lzhaldyb
Rajith Attapattu 2013-03-07 15:58:22 UTC Status ASSIGNED POST
Doc Text Cause:
The URLParser throws an exception if username and password is missing from a connection url.

Consequence:
Due to the exception it's mandatory to specify username/password even if the SASL mech you plan to use does not require it.

Fix:
The URL parser does not thrown an exception if the username or password is missing. Instead it checks if the chosen SASL mechanism (selected during connection negotiation) requires it and then throws an exception at that point.

Result:
Username and password is not mandatory anymore.
Justin Ross 2013-05-21 21:06:49 UTC Fixed In Version 0.22
Irina Boverman 2013-05-31 17:30:03 UTC Status POST MODIFIED
Fixed In Version 0.22 qpid-java-0.22-1.el5, qpid-java-0.22-2.el6
Eric Sammons 2013-07-10 13:33:53 UTC Target Milestone 2.4 3.0
Irina Boverman 2013-07-29 20:09:25 UTC CC iboverma
Irina Boverman 2013-07-29 20:25:02 UTC Status MODIFIED VERIFIED
Justin Ross 2013-09-19 18:17:01 UTC Status VERIFIED ASSIGNED
Rajith Attapattu 2013-09-26 20:38:35 UTC Status ASSIGNED MODIFIED
errata-xmlrpc 2013-10-03 13:59:29 UTC Status MODIFIED ON_QA
Justin Ross 2013-11-11 14:46:05 UTC Status ON_QA VERIFIED
Eric Sammons 2014-07-30 20:37:25 UTC QA Contact mrgqe-bugs messaging-qe-bugs
Michal Toth 2014-09-03 15:28:11 UTC CC mtoth
QA Contact messaging-qe-bugs jross
Leonid Zhaldybin 2014-09-22 09:27:39 UTC Group private
Jared MORGAN 2014-09-23 00:48:48 UTC Doc Text Cause:
The URLParser throws an exception if username and password is missing from a connection url.

Consequence:
Due to the exception, it's mandatory to specify username/password even if the SASL mech you plan to use does not require it.

Fix:
The URL parser does not thrown an exception if the username or password is missing. Instead it checks if the chosen SASL mechanism (selected during connection negotiation) requires it and then throws an exception at that point.

Result:
Username and password is not mandatory anymore. 		It was discovered that the URLParser threw an exception if the username and password was missing from a connection URL. Due to this behavior, it was mandatory to specify a username and password, even if the SASL mechanism chosen did not require it. The URL parser no longer throws an exception if the username or password is missing. Instead it checks if the chosen SASL mechanism (selected during connection negotiation) requires it and then throws an exception at that point.
errata-xmlrpc 2014-09-24 14:40:53 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2014-09-24 15:03:10 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-09-24 11:03:10 UTC

Back to bug 728509