[prev in list] [next in list] [prev in thread] [next in thread]
List: xmlrpc-user
Subject: [jira] [Commented] (WSS-701) Support for X509PKIPathv1 in WSSecEncryptKey is missing
From: "Colm O hEigeartaigh (Jira)" <jira () apache ! org>
Date: 2023-07-27 5:13:00
Message-ID: JIRA.13544450.1689948862000.183277.1690434780011 () Atlassian ! JIRA
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/WSS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747756#comment-17747756 \
]
Colm O hEigeartaigh commented on WSS-701:
-----------------------------------------
Hi, can you submit a pull request for the change?
> Support for X509PKIPathv1 in WSSecEncryptKey is missing
> -------------------------------------------------------
>
> Key: WSS-701
> URL: https://issues.apache.org/jira/browse/WSS-701
> Project: WSS4J
> Issue Type: Improvement
> Components: WSS4J Core
> Affects Versions: 3.0.1
> Reporter: Philip Helger
> Assignee: Colm O hEigeartaigh
> Priority: Major
>
> Hi Colm,
> We stumbled upon another small inconsistency between `WSSecSignature` and \
> `WSSecEncryptedKey`. Via `WSSecSignature.setUseSingleCertificate(boolean)` it is \
> possible to switch between the Binary Security Token types `#X509v3` and \
> `#X509PKIPathv1`. In `WSSecEncryptedKey` the BST is always using the `#X509v3` \
> type. Please add the respective switch between the 2 types also for \
> `WSSecEncryptedKey`. Thanks, Philip
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic