You are viewing a plain text version of this content. The canonical link for it is here.
Posted to wss4j-dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2009/01/05 17:01:44 UTC
[jira] Resolved: (WSS-79) Compatibility issue with weblogic wsse
[ https://issues.apache.org/jira/browse/WSS-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-79.
------------------------------------
Resolution: Won't Fix
Fix Version/s: 1.5.5
> Compatibility issue with weblogic wsse
> --------------------------------------
>
> Key: WSS-79
> URL: https://issues.apache.org/jira/browse/WSS-79
> Project: WSS4J
> Issue Type: Improvement
> Environment: wss4j 1.5.1 weblogic server 8.1 sp6
> Reporter: Willy ANTOINE
> Priority: Minor
> Fix For: 1.5.5
>
>
> Hello
> Some implementations of weblogic server returns only a key name as a security reference.
> When the client use wss4j for decryption, it can handle this.
> When wss4j is used as a client recceiver, it should be able to find the alias from the key name.
> The solution correspond on the code commented in org.apache.ws.security.processor.EncryptedKeyProcessor lines 149-152, 240-244, and in org.apache.ws.security.message.token.SecurityTokenReference, lines 74, 75, 466-472.
> I think, even if this method doesn't allow to identify a unique certificate, it could be activate by a configuration parameter, with some restrictions:
> if the crypto.getAliasesForDN returns more than one certificate, throws an exception.
> Best regards
> Willy
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: wss4j-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: wss4j-dev-help@ws.apache.org