I am seeing this behavior in WildFly 9.0.2.Final using the same technologies with an EAR project. It looks like WF 9.0.2.Final is still using Picketlink 2.7.0.Final so it makes sense that I'm still seeing this issue.

The principal is available in the JSF backing beans and EJBs within the war of the web project, but once it hits the EJB proxy to a resource in the EJB JAR module the principal is not available.

Project structure:

• project.ear
  • project-ejb.jar (principal not available here)
  • project-web.war (correct principal available here)

• Is there any plan to address this in Picketlink for a subsequent WildFly 9 release? (Just trying to decide whether we should plan to postpone our SAML2 integration until WildFly 10 and Elytron+Keycloak)
• Is there any known workaround (even if a bit of a hack) in order to retrieve the correct principal once we hit the EJB module within the EAR?

Thank you in advance for any additional information on this particular issue.