[GLASSFISH-3774] Custom principal does not get propagated into EJB tier by using ProgrammaticLogin Created: 15/Oct/07  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: willtao Assignee: raharsha
Resolution: Unresolved Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: Linux

Issuezilla Id: 3,774


In glassfish V2, custom principal class ( which extends
com.sun.web.security.WebPrincipal or com.sun.enterprise.deployment.Principal)
does not get propagated into ejb tier even this custom principal has been added
into subject in the commit method in the customLoginModule. When it calls
getCallerPrinpical method in ejb tier, it always return

In the src code of glassfish , this com.sun.enterprise.deployment.PrincipalImpl
has been hard coded in few placed which might stop glassfish return correct
custom principal.

Comment by gfbugbridge [ 16/Oct/07 ]


Comment by kumarjayanti [ 30/Oct/07 ]

Moving target to V3. Could not be fixed for UR1 due to other high priority tasks.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Mon Aug 29 05:19:59 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.