ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Commented] (WSS-456) Not possible to support SymmetricBinding ProtectTokens policy
Date Fri, 31 Aug 2018 11:55:00 GMT


Colm O hEigeartaigh commented on WSS-456:

ProtectTokens + SymmericBinding is actually supported for the DOM code, but not the StAX code.
Do you specifically need it for the StAX code?

You can reproduce the error by removing the if statement in this piece of test-code in CXF:


The error that results is " Part to
sign not found: \{}EncryptedKey". The problem is that as
we have "sign before encrypting", the EncryptedKey is not yet available to the Signature when
we are trying to sign the EncryptedKey. It might be possible to get it working with some hacking,
but it would probably be quite tricky.


> Not possible to support SymmetricBinding ProtectTokens policy
> -------------------------------------------------------------
>                 Key: WSS-456
>                 URL:
>             Project: WSS4J
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Marc Giger
>            Priority: Major
> It is not possible currently to support the SymmetricBinding ProtectTokens policy. In
this scenario, the Signature KeyInfo references an EncryptedKey Element, and also signs the
EncryptedKey Element.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message