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

List:       xmlrpc-user
Subject:    [jira] [Closed] (WSS-506) Wss4jSecurityInterceptor.verifyCertificateTrust does not respect validator
From:       "Aslak Os (JIRA)" <jira () apache ! org>
Date:       2014-07-23 10:34:39
Message-ID: JIRA.12729137.1406110277773.28061.1406111679334 () arcas
[Download RAW message or body]


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

Aslak Os closed WSS-506.
------------------------

    Resolution: Invalid

Should be directed to spring-ws not wss4j

> Wss4jSecurityInterceptor.verifyCertificateTrust does not respect validators from \
>                 WSSConfig
> ------------------------------------------------------------------------------------------
>  
> Key: WSS-506
> URL: https://issues.apache.org/jira/browse/WSS-506
> Project: WSS4J
> Issue Type: Bug
> Components: WSS4J Core
> Affects Versions: 2.0.1
> Reporter: Aslak Os
> Assignee: Colm O hEigeartaigh
> 
> While working on a custom certificate trust system. I discovert that in order to \
> supply a custom validator of trust i had to both set it in WSSConfig and override \
> the verifyCertificateTrust method.  The reason is that the verifyCertificateTrust \
> instansiate a Validator hardcoded by name useing its constructor.  I would assume \
> and prefer that it used the configuration set in WSSConfig. How ever it could be \
> that this is done intentionally.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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