You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/02/10 10:49:41 UTC
[jira] [Updated] (DOSGI-182) SecurityContext populated by spring
security made available to CXF
[ https://issues.apache.org/jira/browse/DOSGI-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider updated DOSGI-182:
--------------------------------------
Fix Version/s: (was: 2.1.0)
> SecurityContext populated by spring security made available to CXF
> ------------------------------------------------------------------
>
> Key: DOSGI-182
> URL: https://issues.apache.org/jira/browse/DOSGI-182
> Project: CXF Distributed OSGi
> Issue Type: Wish
> Affects Versions: 1.4.0
> Reporter: Isart
>
> I'd like SecurityContext populated by SpringSecurity filter chain to be available in CXF, and also being available to registered services.
> I've been able to apply a SpringSecurity filter chain to JAX-RS services published with DOSGi by instantiating my filter chain bean and registering it as an
> osgi service with "org.apache.cxf.httpservice.filter" property.
> This filter chain populates SecurityContext but also removes it when the filter chain finishes.
> org.apache.cxf.dosgi.dsw.handlers.SecurityDelegatingHttpContext is responsible of handling the filter for DOSGi registered web services.
> When a request comes, the filter chain finishes before normal request processing in CXF takes place, resulting in SecurityContext not being available in CXF nor in registered web services.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)