Bug 1168595 - Security realm should only map to RealmUser where really required.
Summary: Security realm should only map to RealmUser where really required.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR12
: EAP 6.4.0
Assignee: Darran Lofthouse
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-27 11:21 UTC by Darran Lofthouse
Modified: 2019-08-19 12:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:40:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-286 0 Major Pull Request Sent The SecurityRealmService should only perform a generic mapping to RealmUser if really required. 2014-11-27 11:23:55 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.