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

Bug 1168595

Summary: Security realm should only map to RealmUser where really required.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Darran Lofthouse <darran.lofthouse>
Component: SecurityAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Slavicek <pslavice>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: anmiller, bdawidow, darran.lofthouse, kkhan, okotek, pskopek
Target Milestone: DR12   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:40:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Darran Lofthouse 2014-11-27 11:21:35 UTC 
Description of problem:

There are a couple of ways a RealmUser principal could already exist, the security realm should only be creating one as a last resort.
Comment 2 Ondrej Kotek 2014-12-04 13:13:57 UTC 
Please, could you provide a broader context? In which cases can I verify that the problem is solved?
Comment 3 Darran Lofthouse 2014-12-04 13:26:40 UTC 
I would suggest something like configuring the ApplicationRealm to use LDAP but also configure it to reload the users identity.  

Then use an EJB application and on the remote client and use the username in a different case, in the failure scenario within the application you should see the users identity represented using the case supplied by the remote client, in the success case where the correct RealmUser mapping occurs you should now see the correct case.