[jboss-jira] [JBoss JIRA] (WFLY-3313) Websocket Auth - Container is not aware of the Principal

[Darran Lofthouse (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488601#comment-13488601 ] 

Darran Lofthouse commented on WFLY-3313:
----------------------------------------

Can you please try this on WildFly 11?  If this was present in WildFly 10 it is possible this still is an issue but there has been a lot of rework regarding identity associated in WildFly 11 so would be good to confirm if that is the case.

> Websocket Auth - Container is not aware of the Principal
> --------------------------------------------------------
>
>                 Key: WFLY-3313
>                 URL: https://issues.jboss.org/browse/WFLY-3313
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Security, Web (Undertow), Web Sockets
>    Affects Versions: 8.1.0.CR1, 10.0.0.Final
>            Reporter: Markus D
>            Assignee: Stuart Douglas
>         Attachments: websocket-different-principals-ejb-vs-socket.png
>
>
> The Websocket is protected by the web.xml. The session object of the callback object correctly returns the principal. 
> When an EJB is called the callerPrincipal is always anonymous. 
> @Resource
>    private SessionContext ctx;
> Principal callerPrincipal = ctx.getCallerPrincipal();
> Running thread here:
> https://community.jboss.org/thread/240617
> Shouldn't the principal be propagated to the EJB container when a websocket callback method triggered?



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)