You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Alessio Soldano (JIRA)" <ji...@apache.org> on 2013/08/13 18:23:52 UTC
[jira] [Updated] (WSS-474) Missing the 'EncodingType' attribute in
element built by STRTransformUtil#createBSTX509
[ https://issues.apache.org/jira/browse/WSS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated WSS-474:
--------------------------------
Attachment: STR-KI-REF-EncodingType.diff
Attaching a patch with a proposal for fixing the problem.
> Missing the 'EncodingType' attribute in element built by STRTransformUtil#createBSTX509
> ---------------------------------------------------------------------------------------
>
> Key: WSS-474
> URL: https://issues.apache.org/jira/browse/WSS-474
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.6.9
> Reporter: Alessio Soldano
> Assignee: Colm O hEigeartaigh
> Attachments: STR-KI-REF-EncodingType.diff
>
>
> I have an incoming request that is being rejected due to a failure in signature validation. The message has a signature over a STR (using key identifier) and is produced by a different security engine (Oracle OSB).
> I suspected some issues / different implementations in the canonicalization process, so I checked logs on the client side and finally compared the canonicalized fragments being digested on both sides.
> The problem is that afaics they look different, basically the fragment on server side seem to be missing the 'EncodingType' attribute in the element that's built in WSS4J (1.6.x) STRTransformUtil#createBSTX509.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org