[prev in list] [next in list] [prev in thread] [next in thread] 

List:       webservices-general
Subject:    [jira] [Resolved] (WSS-516) Change saml AssertionWrapper to setSamlVersion before calling callback h
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2014-10-08 10:40:34
Message-ID: JIRA.12746594.1412735671000.216546.1412764834027 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh resolved WSS-516.
-------------------------------------
    Resolution: Fixed

> 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
> Priority: Minor
> Fix For: 1.6.18
> 
> 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: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]