Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080540

Summary: Upgrade JBoss SASL from 1.0.3.Final-redhat-1 to 1.0.4.Final
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Darran Lofthouse <darran.lofthouse>
Component: SecurityAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED CURRENTRELEASE QA Contact: Josef Cacek <jcacek>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: dosoudil, fbogyai, kkhan
Target Milestone: ER1   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-28 15:27:10 UTC Type: Component Upgrade
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1074428    

Description Darran Lofthouse 2014-03-25 16:11:32 UTC 
Description of problem:

In preparation for enabling GSSAPI / Kerberos support the default protocol within JBoss Remoting was changed from 'remote' to 'remoting' when creating the SASL server and client.

For interoperability reasons with different clients we need to be able to support a protocol of 'remote' or 'remoting', this SASL upgrade will enable us to support both.
Comment 1 Darran Lofthouse 2014-03-25 16:12:37 UTC 
Not quite a blocker but this is very closely related to the overall solution for: -
https://bugzilla.redhat.com/show_bug.cgi?id=1074428
Comment 2 Vladimir Dosoudil 2014-03-27 06:48:38 UTC 
Prod rebuild PR: https://github.com/jbossas/jboss-eap/pull/1146
Comment 3 Kabir Khan 2014-03-27 18:02:36 UTC 
Merged 1146 for ER1
Comment 4 FIlip Bogyai 2014-04-08 11:48:39 UTC 
Verified in 6.3.0.ER1