[jira] [Resolved] (WSS-611) CAs with the NameConstraint extension cause exceptions when verifying trust

[ https://issues.apache.org/jira/browse/WSS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-611. - Resolution: Fixed > CAs with the NameConstraint extension cause exceptions when verifying

[jira] [Updated] (WSS-611) CAs with the NameConstraint extension cause exceptions when verifying trust

[ https://issues.apache.org/jira/browse/WSS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-611: Fix Version/s: 2.1.11 > CAs with the NameConstraint extension cause exceptions when verifying

[jira] [Resolved] (WSS-612) CertificateStore crypto implementation does not correctly handle certificate chains

[ https://issues.apache.org/jira/browse/WSS-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-612. - Resolution: Fixed > CertificateStore crypto implementation does not correctly handle

[jira] [Updated] (WSS-613) Update OpenSAMLUtil to be able to sign generic SignableSAMLObjects

[ https://issues.apache.org/jira/browse/WSS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-613: Summary: Update OpenSAMLUtil to be able to sign generic SignableSAMLObjects (was: Updated

[jira] [Comment Edited] (WSS-611) CAs with the NameConstraint extension cause exceptions when verifying trust

[ https://issues.apache.org/jira/browse/WSS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118613#comment-16118613 ] Colm O hEigeartaigh edited comment on WSS-611 at 8/8/17 4:48 PM: - Thanks for

[jira] [Commented] (WSS-611) CAs with the NameConstraint extension cause exceptions when verifying trust

[ https://issues.apache.org/jira/browse/WSS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118613#comment-16118613 ] Colm O hEigeartaigh commented on WSS-611: - Thanks for the PR. Could you separate out the

[jira] [Commented] (WSS-611) CAs with the NameConstraint extension cause exceptions when verifying trust

[ https://issues.apache.org/jira/browse/WSS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16114074#comment-16114074 ] Colm O hEigeartaigh commented on WSS-611: - Yes please attach it as a patch to this JIRA. PRs are fine

[jira] [Resolved] (WSS-610) WSSecurityUtil.decodeAction misbehaving when sending NoSecurity

[ https://issues.apache.org/jira/browse/WSS-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-610. - Resolution: Fixed > WSSecurityUtil.decodeAction misbehaving when sending NoSecurity >

[jira] [Updated] (WSS-610) WSSecurityUtil.decodeAction misbehaving when sending NoSecurity

[ https://issues.apache.org/jira/browse/WSS-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-610: Fix Version/s: 2.1.11 2.0.11 2.2.0 >

[jira] [Commented] (WSS-609) WS-Security Canonicalization with InclusiveNamespace

[ https://issues.apache.org/jira/browse/WSS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072293#comment-16072293 ] Colm O hEigeartaigh commented on WSS-609: - Please don't file a bug to ask a question...that's what

[jira] [Closed] (WSS-606) Possibility to configure the SAML attribute //Assertion/Subject/NameID/@SPProvidedID in a CallbackHandler

[ https://issues.apache.org/jira/browse/WSS-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-606. --- > Possibility to configure the SAML attribute > //Assertion/Subject/NameID/@SPProvidedID in a

[jira] [Closed] (WSS-608) Allow policy tokens not to have a wsp:Policy child element

[ https://issues.apache.org/jira/browse/WSS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-608. --- > Allow policy tokens not to have a wsp:Policy child element >

[jira] [Commented] (WSS-607) Only 2.2.0 Javadocs visible, but 2.1.9 is current version

[ https://issues.apache.org/jira/browse/WSS-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16013732#comment-16013732 ] Colm O hEigeartaigh commented on WSS-607: - The website is generated automatically, so it's hard to

[jira] [Resolved] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit

[ https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-605. - Resolution: Fixed Thanks for the patch. > Ensure the ws-security-dom can work with the saaj

[jira] [Commented] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit

[ https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958976#comment-15958976 ] Colm O hEigeartaigh commented on WSS-605: - Hi [~ffang], With the patch applied, lots of tests are

[jira] [Commented] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit

[ https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957142#comment-15957142 ] Colm O hEigeartaigh commented on WSS-605: - Hi [~ffang], Would it work to replace the following line:

[jira] [Updated] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit

[ https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-605: Fix Version/s: 2.2.0 > Ensure the ws-security-dom can work with the saaj impl in latest Java9

[jira] [Resolved] (WSS-606) Possibility to configure the SAML attribute //Assertion/Subject/NameID/@SPProvidedID in a CallbackHandler

[ https://issues.apache.org/jira/browse/WSS-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-606. - Resolution: Fixed > Possibility to configure the SAML attribute >

[jira] [Closed] (WSS-600) Get the configured ParserPool via OpenSAMLUtil

[ https://issues.apache.org/jira/browse/WSS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-600. --- > Get the configured ParserPool via OpenSAMLUtil > -- >

[jira] [Closed] (WSS-603) Improper date check in SamlAssertionWrapper.checkIssueInstant

[ https://issues.apache.org/jira/browse/WSS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-603. --- > Improper date check in SamlAssertionWrapper.checkIssueInstant >

[jira] [Closed] (WSS-597) Implement equals/hashCode for the WSS4J policy model

[ https://issues.apache.org/jira/browse/WSS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-597. --- > Implement equals/hashCode for the WSS4J policy model >

[jira] [Closed] (WSS-602) ConfigurationConstants.VALIDATOR_MAP is not supported

[ https://issues.apache.org/jira/browse/WSS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-602. --- > ConfigurationConstants.VALIDATOR_MAP is not supported >

[jira] [Closed] (WSS-601) Optionally skip XACML initialization for OpenSAML

[ https://issues.apache.org/jira/browse/WSS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-601. --- > Optionally skip XACML initialization for OpenSAML >

[jira] [Closed] (WSS-558) org.apache.ws.security.message.WSSecSignature can't support custom provider

[ https://issues.apache.org/jira/browse/WSS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-558. --- > org.apache.ws.security.message.WSSecSignature can't support custom provider >

[jira] [Closed] (WSS-604) UsernameTokenNoPassword does not work via WSHandler

[ https://issues.apache.org/jira/browse/WSS-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-604. --- > UsernameTokenNoPassword does not work via WSHandler >

[jira] [Updated] (WSS-606) Possibility to configure the SAML attribute //Assertion/Subject/NameID/@SPProvidedID in a CallbackHandler

[ https://issues.apache.org/jira/browse/WSS-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-606: Fix Version/s: (was: 2.1.9) 2.1.10 > Possibility to configure the SAML

[jira] [Commented] (WSS-605) Ensure the ws-security-dom can work with the saaj impl in latest Java9 EA kit

[ https://issues.apache.org/jira/browse/WSS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15951069#comment-15951069 ] Colm O hEigeartaigh commented on WSS-605: - I think I'd prefer if the method was renamed to

[jira] [Resolved] (WSS-558) org.apache.ws.security.message.WSSecSignature can't support custom provider

[ https://issues.apache.org/jira/browse/WSS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-558. - Resolution: Fixed > org.apache.ws.security.message.WSSecSignature can't support custom

[jira] [Updated] (WSS-558) org.apache.ws.security.message.WSSecSignature can't support custom provider

[ https://issues.apache.org/jira/browse/WSS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-558: Fix Version/s: 2.1.9 2.2.0 > org.apache.ws.security.message.WSSecSignature

[jira] [Closed] (WSS-574) IllegalArgumentException thrown in WSSecEncryptedKey due to incorrect keyAlgorithm

[ https://issues.apache.org/jira/browse/WSS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-574. --- Resolution: Cannot Reproduce > IllegalArgumentException thrown in WSSecEncryptedKey due to

[jira] [Closed] (WSS-547) unreleased resource

[ https://issues.apache.org/jira/browse/WSS-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-547. --- Resolution: Not A Problem > unreleased resource > --- > > Key:

[jira] [Resolved] (WSS-604) UsernameTokenNoPassword does not work via WSHandler

[ https://issues.apache.org/jira/browse/WSS-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-604. - Resolution: Fixed > UsernameTokenNoPassword does not work via WSHandler >

[jira] [Resolved] (WSS-603) Improper date check in SamlAssertionWrapper.checkIssueInstant

[ https://issues.apache.org/jira/browse/WSS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-603. - Resolution: Fixed > Improper date check in SamlAssertionWrapper.checkIssueInstant >

[jira] [Updated] (WSS-603) Improper date check in SamlAssertionWrapper.checkIssueInstant

[ https://issues.apache.org/jira/browse/WSS-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-603: Fix Version/s: 2.1.9 2.0.11 2.2.0 > Improper date check

[jira] [Resolved] (WSS-602) ConfigurationConstants.VALIDATOR_MAP is not supported

[ https://issues.apache.org/jira/browse/WSS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-602. - Resolution: Fixed > ConfigurationConstants.VALIDATOR_MAP is not supported >

[jira] [Resolved] (WSS-601) Optionally skip XACML initialization for OpenSAML

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

[jira] [Resolved] (WSS-600) Get the configured ParserPool via OpenSAMLUtil

[ https://issues.apache.org/jira/browse/WSS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-600. - Resolution: Fixed > Get the configured ParserPool via OpenSAMLUtil >

[jira] [Updated] (WSS-599) Upgrade to Java 8 DateTime API

[ https://issues.apache.org/jira/browse/WSS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-599: Summary: Upgrade to Java 8 DateTime API (was: Upgrade to JAva 8 DateTime API) > Upgrade to

[jira] [Resolved] (WSS-597) Implement equals/hashCode for the WSS4J policy model

[ https://issues.apache.org/jira/browse/WSS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-597. - Resolution: Fixed > Implement equals/hashCode for the WSS4J policy model >

[jira] [Created] (WSS-597) Implement equals/hashCode for the WSS4J policy model

Colm O hEigeartaigh created WSS-597: --- Summary: Implement equals/hashCode for the WSS4J policy model Key: WSS-597 URL: https://issues.apache.org/jira/browse/WSS-597 Project: WSS4J Issue

[jira] [Closed] (WSS-590) WSS4J relies on deafult locale

[ https://issues.apache.org/jira/browse/WSS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-590. --- > WSS4J relies on deafult locale > -- > > Key: WSS-590 >

[jira] [Closed] (WSS-594) Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader element

[ https://issues.apache.org/jira/browse/WSS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-594. --- > Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader element >

[jira] [Closed] (WSS-593) Implement Certificate Issuer DN Constraint support

[ https://issues.apache.org/jira/browse/WSS-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-593. --- > Implement Certificate Issuer DN Constraint support >

[jira] [Closed] (WSS-587) Concurrency issue in EHCacheManagerHolder

[ https://issues.apache.org/jira/browse/WSS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-587. --- > Concurrency issue in EHCacheManagerHolder > - > >

[jira] [Closed] (WSS-585) Kerberos processing fails on HP Java 8.0.06

[ https://issues.apache.org/jira/browse/WSS-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-585. --- > Kerberos processing fails on HP Java 8.0.06 > --- > >

[jira] [Resolved] (WSS-595) NoClassDefFoundError and ClassNotFoundException for WSSecurityException

[ https://issues.apache.org/jira/browse/WSS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-595. - Resolution: Not A Bug > NoClassDefFoundError and ClassNotFoundException for

[jira] [Closed] (WSS-595) NoClassDefFoundError and ClassNotFoundException for WSSecurityException

[ https://issues.apache.org/jira/browse/WSS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-595. --- > NoClassDefFoundError and ClassNotFoundException for WSSecurityException >

[jira] [Resolved] (WSS-596) org.apache.wss4j.common.crypto.CryptoFactory add security provider always

[ https://issues.apache.org/jira/browse/WSS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-596. - Resolution: Fixed > org.apache.wss4j.common.crypto.CryptoFactory add security provider

[jira] [Commented] (WSS-596) org.apache.wss4j.common.crypto.CryptoFactory add security provider always

[ https://issues.apache.org/jira/browse/WSS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15712127#comment-15712127 ] Colm O hEigeartaigh commented on WSS-596: - I'll remove the static call in CryptoFactory for 2.2.0.

[jira] [Updated] (WSS-596) org.apache.wss4j.common.crypto.CryptoFactory add security provider always

[ https://issues.apache.org/jira/browse/WSS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-596: Fix Version/s: 2.2.0 > org.apache.wss4j.common.crypto.CryptoFactory add security provider

[jira] [Commented] (WSS-595) NoClassDefFoundError and ClassNotFoundException for WSSecurityException

[ https://issues.apache.org/jira/browse/WSS-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15708727#comment-15708727 ] Colm O hEigeartaigh commented on WSS-595: - How are you compiling WSS4J and how are you adding it to

[jira] [Resolved] (WSS-594) Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader element

[ https://issues.apache.org/jira/browse/WSS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-594. - Resolution: Fixed > Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader

[jira] [Created] (WSS-594) Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader element

Colm O hEigeartaigh created WSS-594: --- Summary: Copy Security Header SOAP MustUnderstand/Actor to an EncryptedHeader element Key: WSS-594 URL: https://issues.apache.org/jira/browse/WSS-594 Project:

[jira] [Resolved] (WSS-593) Implement Certificate Issuer DN Constraint support

[ https://issues.apache.org/jira/browse/WSS-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-593. - Resolution: Fixed > Implement Certificate Issuer DN Constraint support >

[jira] [Resolved] (WSS-592) Add support for a comma-separated list of crls

[ https://issues.apache.org/jira/browse/WSS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-592. - Resolution: Fixed > Add support for a comma-separated list of crls >

[jira] [Created] (WSS-592) Add support for a comma-separated list of crls

Colm O hEigeartaigh created WSS-592: --- Summary: Add support for a comma-separated list of crls Key: WSS-592 URL: https://issues.apache.org/jira/browse/WSS-592 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-590) WSS4J relies on deafult locale

[ https://issues.apache.org/jira/browse/WSS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-590. - Resolution: Fixed > WSS4J relies on deafult locale > -- > >

[jira] [Closed] (WSS-591) InputStream is not closed

[ https://issues.apache.org/jira/browse/WSS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-591. --- Resolution: Not A Problem > InputStream is not closed > - > >

[jira] [Commented] (WSS-591) InputStream is not closed

[ https://issues.apache.org/jira/browse/WSS-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532216#comment-15532216 ] Colm O hEigeartaigh commented on WSS-591: - It's not closed because it's not created there either.

[jira] [Commented] (WSS-590) WSS4J relies on deafult locale

[ https://issues.apache.org/jira/browse/WSS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529834#comment-15529834 ] Colm O hEigeartaigh commented on WSS-590: - >From what I can see, it's not a requirement that the mime

[jira] [Commented] (WSS-590) WSS4J relies on deafult locale

[ https://issues.apache.org/jira/browse/WSS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529800#comment-15529800 ] Colm O hEigeartaigh commented on WSS-590: - Ok I've changed the logic to use regular expressions in

[jira] [Updated] (WSS-590) WSS4J relies on deafult locale

[ https://issues.apache.org/jira/browse/WSS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-590: Fix Version/s: 2.1.8 2.0.10 2.2.0 > WSS4J relies on

[jira] [Closed] (WSS-589) Incorrect cast in WSHandler getString

[ https://issues.apache.org/jira/browse/WSS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-589. --- > Incorrect cast in WSHandler getString > - > >

[jira] [Resolved] (WSS-589) Incorrect cast in WSHandler getString

[ https://issues.apache.org/jira/browse/WSS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-589. - Resolution: Not A Problem > Incorrect cast in WSHandler getString >

[jira] [Commented] (WSS-589) Incorrect cast in WSHandler getString

[ https://issues.apache.org/jira/browse/WSS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15522636#comment-15522636 ] Colm O hEigeartaigh commented on WSS-589: - It sounds like you might be using the SIG_PROP_REF_ID

[jira] [Closed] (WSS-588) Server-side signature validation on client fail with only certificate CA is in the client truststore

[ https://issues.apache.org/jira/browse/WSS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-588. --- Resolution: Not A Problem Please direct any future questions to the mailing list instead. >

[jira] [Commented] (WSS-588) Server-side signature validation on client fail with only certificate CA is in the client truststore

[ https://issues.apache.org/jira/browse/WSS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513675#comment-15513675 ] Colm O hEigeartaigh commented on WSS-588: - Yes, see here: http://ws.apache.org/wss4j/config.html The

[jira] [Commented] (WSS-588) Server-side signature validation on client fail with only certificate CA is in the client truststore

[ https://issues.apache.org/jira/browse/WSS-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513594#comment-15513594 ] Colm O hEigeartaigh commented on WSS-588: - Hi Claude, This is not a bug. The signing certificate is

[jira] [Commented] (WSS-587) Concurrency issue in EHCacheManagerHolder

[ https://issues.apache.org/jira/browse/WSS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502808#comment-15502808 ] Colm O hEigeartaigh commented on WSS-587: - Ok thanks. Go ahead and backmerge to 2.0.x then I guess.

[jira] [Commented] (WSS-587) Concurrency issue in EHCacheManagerHolder

[ https://issues.apache.org/jira/browse/WSS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15502740#comment-15502740 ] Colm O hEigeartaigh commented on WSS-587: - Is the bug present in 2.0 as well? > Concurrency issue in

[jira] [Resolved] (WSS-586) Don't query a CallbackHandler for a secret key when parsing a SAML Subject for credentials

[ https://issues.apache.org/jira/browse/WSS-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-586. - Resolution: Fixed > Don't query a CallbackHandler for a secret key when parsing a SAML

[jira] [Created] (WSS-586) Don't query a CallbackHandler for a secret key when parsing a SAML Subject for credentials

Colm O hEigeartaigh created WSS-586: --- Summary: Don't query a CallbackHandler for a secret key when parsing a SAML Subject for credentials Key: WSS-586 URL: https://issues.apache.org/jira/browse/WSS-586

[jira] [Resolved] (WSS-585) Kerberos processing fails on HP Java 8.0.06

[ https://issues.apache.org/jira/browse/WSS-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-585. - Resolution: Fixed > Kerberos processing fails on HP Java 8.0.06 >

[jira] [Updated] (WSS-585) Kerberos processing fails on HP Java 8.0.06

[ https://issues.apache.org/jira/browse/WSS-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-585: Fix Version/s: 2.1.8 2.0.10 > Kerberos processing fails on HP Java 8.0.06 >

[jira] [Commented] (WSS-585) Kerberos processing fails on HP Java 8.0.06

[ https://issues.apache.org/jira/browse/WSS-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434655#comment-15434655 ] Colm O hEigeartaigh commented on WSS-585: - Fixed for 2.1.8 + 2.0.10 (1.6.x is no longer supported by

[jira] [Closed] (WSS-583) crypto.verifyTrust can fail when the DN of the issuer is more than once in the truststore

[ https://issues.apache.org/jira/browse/WSS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-583. --- > crypto.verifyTrust can fail when the DN of the issuer is more than once in > the truststore >

[jira] [Closed] (WSS-584) Don't create ReplayCache instances internally

[ https://issues.apache.org/jira/browse/WSS-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-584. --- > Don't create ReplayCache instances internally > - > >

[jira] [Closed] (WSS-582) Don't cache Crypto key references in WSHandler

[ https://issues.apache.org/jira/browse/WSS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-582. --- > Don't cache Crypto key references in WSHandler > -- >

[jira] [Resolved] (WSS-584) Don't create ReplayCache instances internally

[ https://issues.apache.org/jira/browse/WSS-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-584. - Resolution: Fixed > Don't create ReplayCache instances internally >

[jira] [Created] (WSS-584) Don't create ReplayCache instances internally

Colm O hEigeartaigh created WSS-584: --- Summary: Don't create ReplayCache instances internally Key: WSS-584 URL: https://issues.apache.org/jira/browse/WSS-584 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-583) crypto.verifyTrust can fail when the DN of the issuer is more than once in the truststore

[ https://issues.apache.org/jira/browse/WSS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-583. - Resolution: Fixed > crypto.verifyTrust can fail when the DN of the issuer is more than once

[jira] [Updated] (WSS-583) crypto.verifyTrust can fail when the DN of the issuer is more than once in the truststore

[ https://issues.apache.org/jira/browse/WSS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-583: Fix Version/s: 2.1.7 2.2.0 > crypto.verifyTrust can fail when the DN of the

[jira] [Resolved] (WSS-582) Don't cache Crypto key references in WSHandler

[ https://issues.apache.org/jira/browse/WSS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-582. - Resolution: Fixed > Don't cache Crypto key references in WSHandler >

[jira] [Created] (WSS-582) Don't cache Crypto key references in WSHandler

Colm O hEigeartaigh created WSS-582: --- Summary: Don't cache Crypto key references in WSHandler Key: WSS-582 URL: https://issues.apache.org/jira/browse/WSS-582 Project: WSS4J Issue Type: Bug

[jira] [Updated] (WSS-582) Don't cache Crypto key references in WSHandler

[ https://issues.apache.org/jira/browse/WSS-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-582: Fix Version/s: 2.0.9 > Don't cache Crypto key references in WSHandler >

[jira] [Closed] (WSS-575) Support for Digest other than sha1 in xenc:EncryptionMethod

[ https://issues.apache.org/jira/browse/WSS-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-575. --- > Support for Digest other than sha1 in xenc:EncryptionMethod >

[jira] [Closed] (WSS-578) Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT

[ https://issues.apache.org/jira/browse/WSS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-578. --- > Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT >

[jira] [Closed] (WSS-577) Binary compatibility broken between version <=2.1.3 and >=2.1.4 with org.apache.wss4j.dom.WSSecurityEngineResult

[ https://issues.apache.org/jira/browse/WSS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-577. --- > Binary compatibility broken between version <=2.1.3 and >=2.1.4 with >

[jira] [Closed] (WSS-580) ThreadLocalSecurityProvider returns null instead of empty collection

[ https://issues.apache.org/jira/browse/WSS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-580. --- > ThreadLocalSecurityProvider returns null instead of empty collection >

[jira] [Commented] (WSS-581) Decryption fails with cipher not initialized error when multiple attachmments are used

[ https://issues.apache.org/jira/browse/WSS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15344023#comment-15344023 ] Colm O hEigeartaigh commented on WSS-581: - No, the EncryptedData does not need to have a KeyInfo - I

[jira] [Commented] (WSS-581) Decryption fails with cipher not initialized error when multiple attachmments are used

[ https://issues.apache.org/jira/browse/WSS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342108#comment-15342108 ] Colm O hEigeartaigh commented on WSS-581: - The error does not appear to be originating in WSS4J? >

[jira] [Commented] (WSS-581) Decryption fails with cipher not initialized error when multiple attachmments are used

[ https://issues.apache.org/jira/browse/WSS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341431#comment-15341431 ] Colm O hEigeartaigh commented on WSS-581: - What's the full stacktrace? > Decryption fails with

[jira] [Resolved] (WSS-580) ThreadLocalSecurityProvider returns null instead of empty collection

[ https://issues.apache.org/jira/browse/WSS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-580. - Resolution: Fixed > ThreadLocalSecurityProvider returns null instead of empty collection >

[jira] [Updated] (WSS-580) ThreadLocalSecurityProvider returns null instead of empty collection

[ https://issues.apache.org/jira/browse/WSS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-580: Fix Version/s: 2.1.6 2.0.8 2.2.0 >

[jira] [Resolved] (WSS-579) Sample configuration WSS4J with log4j

[ https://issues.apache.org/jira/browse/WSS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-579. - Resolution: Not A Problem > Sample configuration WSS4J with log4j >

[jira] [Closed] (WSS-579) Sample configuration WSS4J with log4j

[ https://issues.apache.org/jira/browse/WSS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-579. --- > Sample configuration WSS4J with log4j > - > >

[jira] [Commented] (WSS-579) Sample configuration WSS4J with log4j

[ https://issues.apache.org/jira/browse/WSS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301787#comment-15301787 ] Colm O hEigeartaigh commented on WSS-579: - There is a log4j configuration file in the WSS4J tests

[jira] [Resolved] (WSS-578) Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT

[ https://issues.apache.org/jira/browse/WSS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-578. - Resolution: Fixed > Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT >

[jira] [Updated] (WSS-578) Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT

[ https://issues.apache.org/jira/browse/WSS-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-578: Fix Version/s: 2.1.6 > Binary compatibility breaks between 2.1.5 and 2.1.6-SNAPSHOT >

[jira] [Commented] (WSS-577) Binary compatibility broken between version <=2.1.3 and >=2.1.4 with org.apache.wss4j.dom.WSSecurityEngineResult

[ https://issues.apache.org/jira/browse/WSS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262503#comment-15262503 ] Colm O hEigeartaigh commented on WSS-577: - You might grab the latest 2.1.x code + try the jar out, in

<    1   2   3   4   5   6   7   8   9   10   >