[jira] [Updated] (WSS-710) Implementation of the configuration options to set KeyDerivation parameters

[ https://issues.apache.org/jira/browse/WSS-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-710: Fix Version/s: 4.0.0 3.0.4 > Implementation of the configuration options

[jira] [Resolved] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-706. - Resolution: Fixed > Support for Key Agreement using ECDH-ES >

[jira] [Resolved] (WSS-709) Add more setter methods for AlgorithmSuite$AlgorithmSuiteType

[ https://issues.apache.org/jira/browse/WSS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-709. - Resolution: Fixed > Add more setter methods for AlgorithmSuite$AlgorithmSuiteType >

[jira] [Updated] (WSS-709) Add more setter methods for AlgorithmSuite$AlgorithmSuiteType

[ https://issues.apache.org/jira/browse/WSS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-709: Fix Version/s: 4.0.0 3.0.3 > Add more setter methods for

[jira] [Commented] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810963#comment-17810963 ] Colm O hEigeartaigh commented on WSS-706: - Yes that kind of workaround would be fine [~jrihtarsic] ,

[jira] [Updated] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-706: Fix Version/s: 3.0.3 > Support for Key Agreement using ECDH-ES >

[jira] [Commented] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810920#comment-17810920 ] Colm O hEigeartaigh commented on WSS-706: - [~jrihtarsic] I committed it to 3.0.x-fixes, however

[jira] [Updated] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-706: Fix Version/s: 4.0.0 > Support for Key Agreement using ECDH-ES >

[jira] [Resolved] (WSS-708) Support for EdDSA keys and ED25519 ED448 and signature algorithm

[ https://issues.apache.org/jira/browse/WSS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-708. - Resolution: Fixed > Support for EdDSA keys and ED25519 ED448 and signature algorithm >

[jira] [Commented] (WSS-706) Support for Key Agreement using ECDH-ES

[ https://issues.apache.org/jira/browse/WSS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807076#comment-17807076 ] Colm O hEigeartaigh commented on WSS-706: - Waiting for a new PR to be created against master branch

[jira] [Updated] (WSS-708) Support for EdDSA keys and ED25519 ED448 and signature algorithm

[ https://issues.apache.org/jira/browse/WSS-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-708: Fix Version/s: 4.0.0 3.0.3 > Support for EdDSA keys and ED25519 ED448 and

[jira] [Closed] (WSS-707) Update Santuario to fix CVE-2023-44483

[ https://issues.apache.org/jira/browse/WSS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-707. --- > Update Santuario to fix CVE-2023-44483 > -- > >

[jira] [Closed] (WSS-705) Add SBOMs to published packages

[ https://issues.apache.org/jira/browse/WSS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-705. --- > Add SBOMs to published packages > --- > > Key:

[jira] [Resolved] (WSS-707) Update Santuario to fix CVE-2023-44483

[ https://issues.apache.org/jira/browse/WSS-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-707. - Resolution: Fixed > Update Santuario to fix CVE-2023-44483 >

[jira] [Created] (WSS-707) Update Santuario to fix CVE-2023-44483

Colm O hEigeartaigh created WSS-707: --- Summary: Update Santuario to fix CVE-2023-44483 Key: WSS-707 URL: https://issues.apache.org/jira/browse/WSS-707 Project: WSS4J Issue Type: Bug

[jira] [Resolved] (WSS-705) Add SBOMs to published packages

[ https://issues.apache.org/jira/browse/WSS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-705. - Resolution: Fixed > Add SBOMs to published packages > --- > >

[jira] [Updated] (WSS-705) Add SBOMs to published packages

[ https://issues.apache.org/jira/browse/WSS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-705: Fix Version/s: (was: 2.3.5) > Add SBOMs to published packages >

[jira] [Created] (WSS-705) Add SBOMs to published packages

Colm O hEigeartaigh created WSS-705: --- Summary: Add SBOMs to published packages Key: WSS-705 URL: https://issues.apache.org/jira/browse/WSS-705 Project: WSS4J Issue Type: Task

[jira] [Updated] (WSS-704) Upgrade to XML Security 4.0.0

[ https://issues.apache.org/jira/browse/WSS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-704: Fix Version/s: 4.0.0 > Upgrade to XML Security 4.0.0 > - > >

[jira] [Created] (WSS-704) Upgrade to XML Security 4.0.0

Colm O hEigeartaigh created WSS-704: --- Summary: Upgrade to XML Security 4.0.0 Key: WSS-704 URL: https://issues.apache.org/jira/browse/WSS-704 Project: WSS4J Issue Type: Task

[jira] [Resolved] (WSS-703) Upgrade to OpenSAML v5

[ https://issues.apache.org/jira/browse/WSS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-703. - Resolution: Fixed > Upgrade to OpenSAML v5 > -- > >

[jira] [Created] (WSS-703) Upgrade to OpenSAML v5

Colm O hEigeartaigh created WSS-703: --- Summary: Upgrade to OpenSAML v5 Key: WSS-703 URL: https://issues.apache.org/jira/browse/WSS-703 Project: WSS4J Issue Type: Task Reporter:

[jira] [Commented] (WSS-702) Process hangs when a signature is added and server not reachable

[ https://issues.apache.org/jira/browse/WSS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766266#comment-17766266 ] Colm O hEigeartaigh commented on WSS-702: - OK closing ticket. > Process hangs when a signature is

[jira] [Resolved] (WSS-702) Process hangs when a signature is added and server not reachable

[ https://issues.apache.org/jira/browse/WSS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-702. - Resolution: Fixed > Process hangs when a signature is added and server not reachable >

[jira] [Commented] (WSS-701) Support for X509PKIPathv1 in WSSecEncryptKey is missing

[ https://issues.apache.org/jira/browse/WSS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747756#comment-17747756 ] Colm O hEigeartaigh commented on WSS-701: - Hi, can you submit a pull request for the change? >

[jira] [Commented] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1772#comment-1772 ] Colm O hEigeartaigh commented on WSS-700: - I've added it for WSSecSignature as requested. >

[jira] [Commented] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1770#comment-1770 ] Colm O hEigeartaigh commented on WSS-700: - [~phax] I'm not sure it makes sense to add a Provider for

[jira] [Closed] (WSS-693) Check for CVE/CVSS scores and fail build is severity is over a threshold

[ https://issues.apache.org/jira/browse/WSS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-693. --- > Check for CVE/CVSS scores and fail build is severity is over a threshold >

[jira] [Closed] (WSS-699) org.apache.wss4j.dom.transform.STRTransform not compliant with Oracle spec

[ https://issues.apache.org/jira/browse/WSS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-699. --- > org.apache.wss4j.dom.transform.STRTransform not compliant with Oracle spec >

[jira] [Closed] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-700. --- > WSSecEncrypt cannot set Security Provider > - > >

[jira] [Resolved] (WSS-699) org.apache.wss4j.dom.transform.STRTransform not compliant with Oracle spec

[ https://issues.apache.org/jira/browse/WSS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-699. - Resolution: Fixed > org.apache.wss4j.dom.transform.STRTransform not compliant with Oracle

[jira] [Updated] (WSS-699) org.apache.wss4j.dom.transform.STRTransform not compliant with Oracle spec

[ https://issues.apache.org/jira/browse/WSS-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-699: Fix Version/s: 2.4.2 3.0.1 > org.apache.wss4j.dom.transform.STRTransform

[jira] [Updated] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-700: Fix Version/s: 3.0.1 > WSSecEncrypt cannot set Security Provider >

[jira] [Resolved] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-700. - Resolution: Fixed > WSSecEncrypt cannot set Security Provider >

[jira] [Commented] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741511#comment-17741511 ] Colm O hEigeartaigh commented on WSS-700: - I added a new constructor for WSSecEncrypt that passes a

[jira] [Updated] (WSS-700) WSSecEncrypt cannot set Security Provider

[ https://issues.apache.org/jira/browse/WSS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-700: Fix Version/s: 2.3.4 2.4.2 > WSSecEncrypt cannot set Security Provider >

[jira] [Resolved] (WSS-693) Check for CVE/CVSS scores and fail build is severity is over a threshold

[ https://issues.apache.org/jira/browse/WSS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-693. - Resolution: Fixed > Check for CVE/CVSS scores and fail build is severity is over a

[jira] [Updated] (WSS-693) Check for CVE/CVSS scores and fail build is severity is over a threshold

[ https://issues.apache.org/jira/browse/WSS-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-693: Fix Version/s: 2.3.4 2.4.2 > Check for CVE/CVSS scores and fail build is

[jira] [Closed] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-687. --- > Upgrade OpenSAML to v4.1.x > -- > > Key: WSS-687 >

[jira] [Closed] (WSS-695) Unmarshalling failure with OpenSAML 4

[ https://issues.apache.org/jira/browse/WSS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-695. --- > Unmarshalling failure with OpenSAML 4 > - > >

[jira] [Closed] (WSS-694) Move wss4j to native jakarta namespace

[ https://issues.apache.org/jira/browse/WSS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-694. --- > Move wss4j to native jakarta namespace > -- > >

[jira] [Closed] (WSS-696) Upgrade ehcache to 3.10.0 with jakarta classfier

[ https://issues.apache.org/jira/browse/WSS-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-696. --- > Upgrade ehcache to 3.10.0 with jakarta classfier >

[jira] [Resolved] (WSS-698) No way to call requestData.setSignatureProvider() in WSS4JOutInterceptor and WSS4JInInterceptor

[ https://issues.apache.org/jira/browse/WSS-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-698. - Resolution: Not A Problem You have the option of overriding the WSHandler

[jira] [Commented] (WSS-697) OpenSAMLUtil overrides OpenSAML configured by OpenSAML’s InitializationService

[ https://issues.apache.org/jira/browse/WSS-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535116#comment-17535116 ] Colm O hEigeartaigh commented on WSS-697: - What change do you suggest to be made to how the manually

[jira] [Resolved] (WSS-696) Upgrade ehcache to 3.10.0 with jakarta classfier

[ https://issues.apache.org/jira/browse/WSS-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-696. - Resolution: Fixed > Upgrade ehcache to 3.10.0 with jakarta classfier >

[jira] [Resolved] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-687. - Resolution: Fixed > Upgrade OpenSAML to v4.1.x > -- > >

[jira] [Updated] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-687: Fix Version/s: 3.0.0 > Upgrade OpenSAML to v4.1.x > -- > >

[jira] [Commented] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522800#comment-17522800 ] Colm O hEigeartaigh commented on WSS-687: - That's a good idea Rob. I'm not concerned about the issue

[jira] [Commented] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522265#comment-17522265 ] Colm O hEigeartaigh commented on WSS-687: - Is there a way we can only get the Opensaml artifacts

[jira] [Resolved] (WSS-695) Unmarshalling failure with OpenSAML 4

[ https://issues.apache.org/jira/browse/WSS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-695. - Resolution: Fixed > Unmarshalling failure with OpenSAML 4 >

[jira] [Created] (WSS-695) Unmarshalling failure with OpenSAML 4

Colm O hEigeartaigh created WSS-695: --- Summary: Unmarshalling failure with OpenSAML 4 Key: WSS-695 URL: https://issues.apache.org/jira/browse/WSS-695 Project: WSS4J Issue Type: Improvement

[jira] [Commented] (WSS-655) Support outbound Streaming WS-Security MTOM

[ https://issues.apache.org/jira/browse/WSS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516927#comment-17516927 ] Colm O hEigeartaigh commented on WSS-655: - It can be tested against the "DOM" implementation, which

[jira] [Resolved] (WSS-694) Move wss4j to native jakarta namespace

[ https://issues.apache.org/jira/browse/WSS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-694. - Resolution: Fixed > Move wss4j to native jakarta namespace >

[jira] [Updated] (WSS-694) Move wss4j to native jakarta namespace

[ https://issues.apache.org/jira/browse/WSS-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-694: Fix Version/s: 3.0.0 > Move wss4j to native jakarta namespace >

[jira] [Resolved] (WSS-690) No bundle jar available for Apache WSS4J » 2.4.0

[ https://issues.apache.org/jira/browse/WSS-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-690. - Resolution: Won't Fix > No bundle jar available for Apache WSS4J » 2.4.0 >

[jira] [Commented] (WSS-690) No bundle jar available for Apache WSS4J » 2.4.0

[ https://issues.apache.org/jira/browse/WSS-690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17445760#comment-17445760 ] Colm O hEigeartaigh commented on WSS-690: - We don't ship a binary distribution any more, as projects

[jira] [Commented] (WSS-643) NullPointerException in getCacheManager

[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17434353#comment-17434353 ] Colm O hEigeartaigh commented on WSS-643: - The NPE only happens when there is a problem with setting

[jira] [Commented] (WSS-688) Signatures created with Merlin start being invalid after changing key-store a few times

[ https://issues.apache.org/jira/browse/WSS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17415406#comment-17415406 ] Colm O hEigeartaigh commented on WSS-688: - The signature verification errors would appear in Apache

[jira] [Commented] (WSS-688) Signatures created with Merlin start being invalid after changing key-store a few times

[ https://issues.apache.org/jira/browse/WSS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17408865#comment-17408865 ] Colm O hEigeartaigh commented on WSS-688: - If you turn on debug logging you should see exactly where

[jira] [Commented] (WSS-688) Signatures created with Merlin start being invalid after changing key-store a few times

[ https://issues.apache.org/jira/browse/WSS-688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17407094#comment-17407094 ] Colm O hEigeartaigh commented on WSS-688: - What stack trace do you see in the logs when it starts

[jira] [Commented] (WSS-687) Upgrade OpenSAML to v4.1.x

[ https://issues.apache.org/jira/browse/WSS-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396679#comment-17396679 ] Colm O hEigeartaigh commented on WSS-687: - WSS4J master (2.5.0-SNAPSHOT) has moved to Java 11

[jira] [Resolved] (WSS-686) org.apache.ws.security.util.XmlSchemaDateFormat no longer in 2.3.x

[ https://issues.apache.org/jira/browse/WSS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-686. - Resolution: Won't Fix > org.apache.ws.security.util.XmlSchemaDateFormat no longer in 2.3.x

[jira] [Commented] (WSS-686) org.apache.ws.security.util.XmlSchemaDateFormat no longer in 2.3.x

[ https://issues.apache.org/jira/browse/WSS-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17359817#comment-17359817 ] Colm O hEigeartaigh commented on WSS-686: - It was removed as part of

[jira] [Closed] (WSS-685) Signature before timestamp results in signing after encryption

[ https://issues.apache.org/jira/browse/WSS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-685. --- > Signature before timestamp results in signing after encryption >

[jira] [Resolved] (WSS-685) Signature before timestamp results in signing after encryption

[ https://issues.apache.org/jira/browse/WSS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-685. - Resolution: Fixed > Signature before timestamp results in signing after encryption >

[jira] [Updated] (WSS-685) Signature before timestamp results in signing after encryption

[ https://issues.apache.org/jira/browse/WSS-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-685: Fix Version/s: 2.3.2 > Signature before timestamp results in signing after encryption >

[jira] [Resolved] (WSS-684) Support OpenSaml 4

[ https://issues.apache.org/jira/browse/WSS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-684. - Resolution: Fixed > Support OpenSaml 4 > -- > > Key:

[jira] [Work started] (WSS-684) Support OpenSaml 4

[ https://issues.apache.org/jira/browse/WSS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on WSS-684 started by Colm O hEigeartaigh. --- > Support OpenSaml 4 > -- > > Key: WSS-684 >

[jira] [Commented] (WSS-684) Support OpenSaml 4

[ https://issues.apache.org/jira/browse/WSS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313023#comment-17313023 ] Colm O hEigeartaigh commented on WSS-684: - I'll target this for a new major release which will drop

[jira] [Updated] (WSS-684) Support OpenSaml 4

[ https://issues.apache.org/jira/browse/WSS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-684: Fix Version/s: 2.5.0 > Support OpenSaml 4 > -- > > Key:

[jira] [Commented] (WSS-683) WSS4J depends on Velocity 1.7 which contains a security vulnerability (CVE-2020-13936)

[ https://issues.apache.org/jira/browse/WSS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17312907#comment-17312907 ] Colm O hEigeartaigh commented on WSS-683: - Yes, it appears that dependency exclusion does not work

[jira] [Commented] (WSS-683) WSS4J depends on Velocity 1.7 which contains a security vulnerability (CVE-2020-13936)

[ https://issues.apache.org/jira/browse/WSS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308429#comment-17308429 ] Colm O hEigeartaigh commented on WSS-683: - [~kraberus] - Where is WSS_Sample.zip? > WSS4J depends

[jira] [Commented] (WSS-683) WSS4J depends on Velocity 1.7 which contains a security vulnerability (CVE-2020-13936)

[ https://issues.apache.org/jira/browse/WSS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306034#comment-17306034 ] Colm O hEigeartaigh commented on WSS-683: - Can you attach a sample gradle project that I can use to

[jira] [Commented] (WSS-683) WSS4J depends on Velocity 1.7 which contains a security vulnerability (CVE-2020-13936)

[ https://issues.apache.org/jira/browse/WSS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17304766#comment-17304766 ] Colm O hEigeartaigh commented on WSS-683: - [~kraberus] - WSS4J excludes Velocity from OpenSAML:

[jira] [Deleted] (WSS-682) FREE V-BUCKS GENERATOR 2021 official legit #FORTNITE FREE VBUCKS CODES GENERATOR NO VERIFICATION

[ https://issues.apache.org/jira/browse/WSS-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh deleted WSS-682: > FREE V-BUCKS GENERATOR 2021 official legit #FORTNITE FREE VBUCKS CODES > GENERATOR NO

[jira] [Deleted] (WSS-681) FREE ROBUX GENERATOR 2021 official legit #ROBLOX FREE ROBUX GENERATOR NO VERIFICATION

[ https://issues.apache.org/jira/browse/WSS-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh deleted WSS-681: > FREE ROBUX GENERATOR 2021 official legit #ROBLOX FREE ROBUX GENERATOR NO > VERIFICATION >

[jira] [Resolved] (WSS-680) Usage of broken hash algorithm detected

[ https://issues.apache.org/jira/browse/WSS-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-680. - Resolution: Won't Fix That class uses SHA-1 as per (old) specs. > Usage of broken hash

[jira] [Closed] (WSS-677) Comparison in validate class is vulnerable to timing side channels

[ https://issues.apache.org/jira/browse/WSS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-677. --- > Comparison in validate class is vulnerable to timing side channels >

[jira] [Closed] (WSS-679) Fix regression in signing KeyInfos

[ https://issues.apache.org/jira/browse/WSS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-679. --- > Fix regression in signing KeyInfos > -- > > Key:

[jira] [Closed] (WSS-673) Using default Java Security and Merlin is very slow for PKCS12

[ https://issues.apache.org/jira/browse/WSS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-673. --- > Using default Java Security and Merlin is very slow for PKCS12 >

[jira] [Closed] (WSS-672) Make sure to process all elements of the SAML Signature KeyInfo

[ https://issues.apache.org/jira/browse/WSS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-672. --- > Make sure to process all elements of the SAML Signature KeyInfo >

[jira] [Closed] (WSS-670) Expected signature algorithm is overwriten with default in case of DSA and EC Keys

[ https://issues.apache.org/jira/browse/WSS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-670. --- > Expected signature algorithm is overwriten with default in case of DSA and EC > Keys >

[jira] [Closed] (WSS-678) OpenSAML Decrypter initialization failed

[ https://issues.apache.org/jira/browse/WSS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-678. --- > OpenSAML Decrypter initialization failed > > >

[jira] [Commented] (WSS-618) Cannot create signature which includes KeyInfo

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241636#comment-17241636 ] Colm O hEigeartaigh commented on WSS-618: - The regression was caused by a change in Santuario, but

[jira] [Commented] (WSS-618) Cannot create signature which includes KeyInfo

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241560#comment-17241560 ] Colm O hEigeartaigh commented on WSS-618: - [~rvdpoll] The fix is in WSS4J, not xmlsec. I hope to cut

[jira] [Resolved] (WSS-679) Fix regression in signing KeyInfos

[ https://issues.apache.org/jira/browse/WSS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-679. - Resolution: Fixed > Fix regression in signing KeyInfos > --

[jira] [Commented] (WSS-618) Cannot create signature which includes KeyInfo

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17241460#comment-17241460 ] Colm O hEigeartaigh commented on WSS-618: - [~rvdpoll] - Fixed here:

[jira] [Created] (WSS-679) Fix regression in signing KeyInfos

Colm O hEigeartaigh created WSS-679: --- Summary: Fix regression in signing KeyInfos Key: WSS-679 URL: https://issues.apache.org/jira/browse/WSS-679 Project: WSS4J Issue Type: Improvement

[jira] [Commented] (WSS-618) Cannot create signature which includes KeyInfo

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224552#comment-17224552 ] Colm O hEigeartaigh commented on WSS-618: - It looks like this functionality was broken by this

[jira] [Resolved] (WSS-678) OpenSAML Decrypter initialization failed

[ https://issues.apache.org/jira/browse/WSS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-678. - Resolution: Fixed > OpenSAML Decrypter initialization failed >

[jira] [Updated] (WSS-678) OpenSAML Decrypter initialization failed

[ https://issues.apache.org/jira/browse/WSS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-678: Fix Version/s: 2.4.0 > OpenSAML Decrypter initialization failed >

[jira] [Commented] (WSS-678) OpenSAML Decrypter initialization failed

[ https://issues.apache.org/jira/browse/WSS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186451#comment-17186451 ] Colm O hEigeartaigh commented on WSS-678: - Probably it makes sense to delay updating to WSS4J 2.3.x

[jira] [Commented] (WSS-678) OpenSAML Decrypter initialization failed

[ https://issues.apache.org/jira/browse/WSS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186316#comment-17186316 ] Colm O hEigeartaigh commented on WSS-678: - Is this a bug in the context of WS-Security though? >

[jira] [Resolved] (WSS-677) Comparison in validate class is vulnerable to timing side channels

[ https://issues.apache.org/jira/browse/WSS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-677. - Resolution: Fixed Thanks for reporting, I have migrated instead to use the JDK

[jira] [Updated] (WSS-677) Comparison in validate class is vulnerable to timing side channels

[ https://issues.apache.org/jira/browse/WSS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-677: Fix Version/s: 2.3.1 2.2.6 > Comparison in validate class is vulnerable to

[jira] [Resolved] (WSS-676) CertificateStore should support ALIAS CryptoType

[ https://issues.apache.org/jira/browse/WSS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-676. - Resolution: Won't Fix > CertificateStore should support ALIAS CryptoType >

[jira] [Commented] (WSS-676) CertificateStore should support ALIAS CryptoType

[ https://issues.apache.org/jira/browse/WSS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17158969#comment-17158969 ] Colm O hEigeartaigh commented on WSS-676: - CertificateStore does not support the concept of "alias",

[jira] [Resolved] (WSS-675) WSS4J 2.3.0 exposes Guava

[ https://issues.apache.org/jira/browse/WSS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-675. - Resolution: Not A Problem > WSS4J 2.3.0 exposes Guava > - > >

[jira] [Commented] (WSS-675) WSS4J 2.3.0 exposes Guava

[ https://issues.apache.org/jira/browse/WSS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144666#comment-17144666 ] Colm O hEigeartaigh commented on WSS-675: - There was a compile time dependency on Guava in previous

[jira] [Commented] (WSS-674) How to get WSS4j 2.3.0 jar

[ https://issues.apache.org/jira/browse/WSS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141743#comment-17141743 ] Colm O hEigeartaigh commented on WSS-674: - Please don't use Jira to ask questions, that's what the

  1   2   3   4   5   6   7   8   9   10   >