[
https://issues.apache.org/jira/browse/RAMPART-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved RAMPART-289.
-------------------------------------
Resolution: Fixed
Fixed on master in 318a6555. The RAMPART-278 part of the attached patch has
been in PolicyBasedResultsValidator for years.
Re-testing the rest showed the opposite problem from the one described: under
sp:EncryptBeforeSigning the asymmetric builder
only encrypted supporting tokens when the signature was also encrypted, and
the symmetric builder encrypted the body twice
instead of the tokens, so Encrypted*SupportingTokens were sent in the clear.
The validator never checked the four encrypted
supporting-token kinds, so neither a missing nor a clear-text token was
refused. Both builders now encrypt the tokens in
either protection order, the validator requires the tokens and checks that
they arrived encrypted, and a UsernameToken with
sp:NoPassword is recognised. Covered by
EncryptBeforeSigningSupportingTokensTest. Will ship in 2.0.0.
> PolicyBasedResultsValidator Incorrectly Invalidates Supporting Token
> Signatures/Encryptions and Encrypted Supporting Tokens
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-289
> URL: https://issues.apache.org/jira/browse/RAMPART-289
> Project: Rampart
> Issue Type: Bug
> Affects Versions: 1.5
> Reporter: todd wolff
> Assignee: Robert Lazarski
> Priority: Major
> Labels: Patch
> Fix For: 2.0.0
>
> Attachments: SupportingTokens.patch, SupportingTokens.patch
>
>
> When encrypting/signing a request using supporting tokens,
> PolicyBasedResultsValidator incorrectly invalidates and throws an exception.
> This class also incorrectly invalidates encrypted supporting tokens. I am
> attaching a patch which fixes problem. Note that this patch also includes
> modifications related to issue RAMPART-278.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]