ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (WSS-461) org.apache.ws.security.processor.SignatureProcessor does not allow to add custom resolver
Date Fri, 24 Mar 2017 11:40:41 GMT

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

Colm O hEigeartaigh closed WSS-461.
-----------------------------------
    Resolution: Won't Fix

SignatureProcessor no longer uses the Santuario API for XML Signature.

> org.apache.ws.security.processor.SignatureProcessor does not allow to add custom resolver
> -----------------------------------------------------------------------------------------
>
>                 Key: WSS-461
>                 URL: https://issues.apache.org/jira/browse/WSS-461
>             Project: WSS4J
>          Issue Type: Improvement
>          Components: WSS4J Core
>    Affects Versions: 1.5.12
>            Reporter: Namrata Jaiswal
>            Assignee: Colm O hEigeartaigh
>            Priority: Critical
>
> org.apache.ws.security.processor.SignatureProcessor does not provide api to add resource
resolver. To explain it more,
> I received a soap message with a particular ID pattern and for that ID pattern, I would
like to provide my own implementation for ResourceResolverSpi( that can be added to resource
signature element). If some api is exposed that allows user to provide their own implementation
for resourceresolver then it would great.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message