[
https://issues.apache.org/jira/browse/CAMEL-7078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851780#comment-13851780
]
Sergey Beryozkin commented on CAMEL-7078:
-----------------------------------------
Ouch, I see I created a patch against a SVN based 2.12-SNAPSHOT.
So SVN patched are not accepted any more ? I can do a git-based one, should it
be a pull request or a diff will do ?
Or may be you can try to adapt this time ? the test changes should be OK,
indeed there could be some mismatch on the default CXF mapper level
If you'd like me do another GIT patch, what form it should take, the reflection
code moved to the helper class ?
Cheers, Sergey
> camel-cxf-transport component should propagate SecurityContext
> --------------------------------------------------------------
>
> Key: CAMEL-7078
> URL: https://issues.apache.org/jira/browse/CAMEL-7078
> Project: Camel
> Issue Type: Improvement
> Components: camel-cxf
> Reporter: Sergey Beryozkin
> Assignee: Willem Jiang
> Fix For: 2.11.4, 2.12.3, 2.13.0
>
> Attachments: camel7078-optionalservletdeps.txt,
> camel7078-reflection.txt
>
>
> Camel CXF Transport does not propagate a security context available from the
> current HTTP Servlet Request - which may be wrapped by Spring security, etc.
> Camel users may still work directly with Camel Exchange properties, but CXF
> endpoints won't be able to avoid losing the transport-independent approach
> for checking the security contexts.
>
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
