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

List:       xmlrpc-user
Subject:    [jira] [Closed] (WSS-658) Enable signature confirmation for signed SAML tokens
From:       "Colm O hEigeartaigh (Jira)" <jira () apache ! org>
Date:       2020-03-18 7:18:00
Message-ID: JIRA.13266628.1573058329000.84356.1584515880595 () Atlassian ! JIRA
[Download RAW message or body]


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

Colm O hEigeartaigh closed WSS-658.
-----------------------------------

> Enable signature confirmation for signed SAML tokens
> ----------------------------------------------------
> 
> Key: WSS-658
> URL: https://issues.apache.org/jira/browse/WSS-658
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Fix For: 2.3.0, 2.2.5
> 
> 
> Currently we don't use SAML signatures as part of SignatureConfirmation (either \
> storing the signatures on the sending side, to compare to what comes back, or else \
> sending the values back in the SignatureConfirmation element). This task is to fix \
> this so that it works the same way as for plain Signature elements in the security \
> header.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
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] 

Configure | About | News | Add a list | Sponsored by KoreLogic