Bug 1168585 - The RemotingLoginModule should give priority to the RealmUser in the SubjectUserInfo
Summary: The RemotingLoginModule should give priority to the RealmUser in the SubjectU...
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 10:54 UTC by Darran Lofthouse
Modified: 2019-08-19 12:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:41:02 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-4129 0 Major Pull Request Sent The RemotingLoginModule should first check if there is already a RealmUser 2014-11-27 10:56:13 UTC

Description Darran Lofthouse 2014-11-27 10:54:50 UTC 
Description of problem:

The realm may have already performed a mapping for the username so priority should be given to this.

As an example if the realm has been configured to strip the realm name from the identity of a user authenticated using GSSAPI then by the time it reaches the EJB call the username should not contain the realm name.
Note You need to log in before you can comment on or make changes to this bug.