If a client <-> server authentication negotiation process fails for a certain SASL auth mechanism, then the client re-sends its CAPABILITIES to the server. However, due to a bug in remoting, those CAPABILITIES get ignored and as a result the remoting channel that gets created won't be aware of the client CAPABILITIES. This will lead to the issue that's explained in https://issues.jboss.org/browse/REM3-169. A pull request containing a fix for this, has been issued against remoting upstream https://github.com/jboss-remoting/jboss-remoting/pull/8.
Marked as "urgent" for EAP 6.1.0 as per Jason's suggestion.
David Lloyd <david.lloyd> updated the status of jira REM3-169 to Resolved
Pull req. submitted for updated Remoting version.
This fix will require only the server to be updated, not the client.
We need QE to ack before we can merge a fix. Note that the fix is still undergoing testing.
BTW the testing has passed. We are just missing the QE ack to fix this problem. The issue was raised by GSS. It is affecting customers on 6.0
Moving to MODIFIED as https://github.com/jbossas/jboss-eap/pull/6 was merged several weeks ago.
verified with EAP 6.1.0.ER3