[
https://issues.apache.org/jira/browse/CXF-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854062#action_12854062
]
Sergey Beryozkin commented on CXF-2754:
---------------------------------------
Hi Dan, this is helpful, thanks.
I have extended WSS4JInInterceptor and have few tests (digest, encrypted +
digest, clear text, encrypted + clear text) but I will also work on a case with
a UserName token policy only, before closing this JIRA.
I will do the merge shortly, I will welcome the feedback on what I've done so
far.
cheers, Sergey
> Extend WS-Security component for higher level containers be able to use
> UsernameToken to authenticate a user and populate SecurityContext
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CXF-2754
> URL: https://issues.apache.org/jira/browse/CXF-2754
> Project: CXF
> Issue Type: Improvement
> Components: WS-* Components
> Affects Versions: 2.3, 2.2.8
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Fix For: 2.3, 2.2.8
>
>
> By default, WSS4JInInterceptor relies on CallbackHandlers to provide or
> validate a password for handling digests and clear-texts respectively.
> Also, the default SecurityContext is partially populated and thus can not be
> used for the authorization decisions.
> Higher level containers should be able to delegate to their own subsystems
> for authenticating a user and populating SecurityContext
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
