[
https://issues.apache.org/jira/browse/CXF-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189994#comment-14189994
]
Sergey Beryozkin commented on CXF-6072:
---------------------------------------
Actually, I think you are right, AbstractHttpDestination does delegate to the
request to check the roles a given principal is in but does not to get the
actual Principal, it is just not clear to me why it makes a difference in your
case, typilcally, if a servlet-based security is enforced, then Principal would
already be set up, I guess it is something specific to the way it is integrated
into TomEE...
Either way, delegating to the request is indeed the right fix IMHO
> jaxrs securityContext.getUserPrincipal is broken if login is done during the
> request
> ------------------------------------------------------------------------------------
>
> Key: CXF-6072
> URL: https://issues.apache.org/jira/browse/CXF-6072
> Project: CXF
> Issue Type: Bug
> Reporter: Romain Manni-Bucau
>
> Hi
> tested on last 2.6 release and didn't take time to check on 3. but I guess it
> is the same:
> I call a rest endpoint, in my business I login(user, pass) from the request
> (http) then from the security context I get the principal -> null, if I get
> it fro mthe request it is avlued. It is cause
> org.apache.cxf.transport.http.AbstractHTTPDestination#setupMessage(org.apache.cxf.message.Message,
> javax.servlet.ServletConfig, javax.servlet.ServletContext,
> javax.servlet.http.HttpServletRequest,
> javax.servlet.http.HttpServletResponse) stores the principal for the request
> but it evaluates it too early.
> Why not keeping the delegation to the http request?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
