[
https://issues.apache.org/jira/browse/WSS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163017#comment-14163017
]
Jason Pell commented on WSS-516:
--------------------------------
I started looking at what would be required to do this for wss3j 2.0 and I am
lost, I will continue to investigate if its possible to pass the WS-Policy
derived saml version into the callback, but so far its not clear how that can
be done.
> Change saml AssertionWrapper to setSamlVersion before calling callback handler
> ------------------------------------------------------------------------------
>
> Key: WSS-516
> URL: https://issues.apache.org/jira/browse/WSS-516
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 2.0.2, 1.6.17
> Reporter: Jason Pell
> Assignee: Colm O hEigeartaigh
> Fix For: 1.6.18, 2.0.3
>
> Attachments: patch-1.6.txt
>
>
> If the SAMLCallback was provided the expected Saml Version based on
> information already provided to the AssertionWrapper, it would be easy for a
> local SAMLCallback to create the correct saml token.
> For most everything in CXF we can use the WS-Policy to determine what needs
> to be done on the client side to correct interface with a cxf web service.
> With this small change a SAML Callback handler can create the appropriately
> versioned saml token without additional configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
