SessionContext.getCallerPrincipal not returning custom principal on JBoss EAP 5

Solution Verified - Updated -

Issue

  • After migrating to JBoss EAP 5.0, any session bean that invokes SessionContext.getCallerPrincipal() returns an instance of org.jboss.security.SimplePrincipal and not the custom class specified in the login module configuration where the custom class is specified in the login module, for example,

    <module-option name="principalClass">example.CustomPrincipal</module-option>
    

Environment

  • JBoss Enterprise Application Platform (EAP)
    • 5.0.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content