[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 WSHand

[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 S

Re: [VOTE] - Release Apache WSS4J 2.1.9

ed Hat > > > > On Mar 29, 2017, at 5:57 PM, Colm O hEigeartaigh <cohei...@apache.org> > wrote: > > This is a vote to release Apache WSS4J 2.1.9. > > Issues fixed: > > https://issues.apache.org/jira/browse/WSS/fixforversion/12338825 > > SVN tag: &g

[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

[VOTE] - Release Apache WSS4J 2.1.9

me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[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 cus

[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.WSSecSignat

[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

[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 > --- > >

[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 WSHand

[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.checkIssueInst

[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 ch

[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 suppor

Re: wss4j 2.1.8 binary for Windows

.1.8 JAR > with all its dependencies for Windows. I am facing so many problems with > ad-hoc versions and also not getting the latest binary. Please help. > > > > Regards, > > Neelakanth > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[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 OpenS

[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 OpenSAMLU

[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) > Upgr

[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 mo

[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 > -- > >

[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 elem

[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 supp

[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 EHCacheManagerHol

[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

Re: [VOTE] - Release Apache WSS4J 2.0.10

With 3 binding +1 votes, and no other votes, this vote passes. I'll do the release. Colm. On Mon, Dec 5, 2016 at 2:39 PM, Daniel Kulp <dk...@apache.org> wrote: > +1 > > Dan > > > > On Dec 5, 2016, at 7:58 AM, Colm O hEigeartaigh <cohei...@apache.org> > wrot

Re: [VOTE] - Release Apache WSS4J 2.1.8

With 3 binding +1 votes, and no other votes, this vote passes. I'll do the release. Colm. On Mon, Dec 5, 2016 at 2:39 PM, Daniel Kulp <dk...@apache.org> wrote: > +1 > > Dan > > > > > On Dec 5, 2016, at 7:43 AM, Colm O hEigeartaigh <cohei...@apache.org> > w

[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 ClassNotFoundExcept

[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 WSSecurityExcept

[VOTE] - Release Apache WSS4J 2.0.10

from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[VOTE] - Release Apache WSS4J 2.1.8

me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[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 provi

[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 provi

[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

[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 EncryptedHea

[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 supp

[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 c

[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 loc

[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 clo

[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 m

[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

[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 rel

[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 getStr

[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 getStr

[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

[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

[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 is

[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 S

[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

[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

[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

[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 trus

[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 interna

[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 WSHand

Re: [VOTE] - Release Apache WSS4J 2.0.9

With 4 binding +1 votes, and no other votes, this vote passes. Colm. On Mon, Jul 25, 2016 at 4:48 PM, Alessio Soldano <asold...@redhat.com> wrote: > +1 > > > Il 22/07/2016 18:10, Colm O hEigeartaigh ha scritto: > > This is a vote to release Apache WSS4J 2.0.9. It cont

Re: [VOTE] - Release Apache WSS4J 2.1.7

With 4 binding +1 votes, and no other votes, this vote passes. Colm. On Mon, Jul 25, 2016 at 4:48 PM, Alessio Soldano <asold...@redhat.com> wrote: > +1 > > > Il 22/07/2016 18:03, Colm O hEigeartaigh ha scritto: > > This is a vote to release Apache WSS4J 2.1.7. It cont

[VOTE] - Release Apache WSS4J 2.0.9

/repositories/orgapachews-1045/ Tag: https://svn.apache.org/repos/asf/webservices/wss4j/tags/wss4j-2.0.9/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[VOTE] - Release Apache WSS4J 2.1.7

/repositories/orgapachews-1044/ Tag: https://svn.apache.org/repos/asf/webservices/wss4j/tags/wss4j-2.1.7/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[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 interna

[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 o

[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

[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 WSHand

[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 WSHand

[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:EncryptionMet

[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-SNAPS

[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 &

[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 collect

Re: [VOTE] - Release Apache WSS4J 2.1.6

With 4 binding +1 votes, and one other +1 vote, this vote passes. I'll promote the release. Colm. On Tue, Jun 21, 2016 at 4:52 PM, Daniel Kulp <dk...@apache.org> wrote: > +1 > > Dan > > > > On Jun 20, 2016, at 7:54 AM, Colm O hEigeartaigh <cohei...@apache.org>

Re: [VOTE] - Release Apache WSS4J 2.0.8

With 4 binding +1 votes, and one other +1 vote, this vote passes. I'll promote the release. Colm. On Tue, Jun 21, 2016 at 4:52 PM, Daniel Kulp <dk...@apache.org> wrote: > +1 > > Dan > > > On Jun 20, 2016, at 8:11 AM, Colm O hEigeartaigh <cohei...@apache.org> &

[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 fa

[VOTE] - Release Apache WSS4J 2.0.8

/wss4j/tags/wss4j-2.0.8/ Artifacts: https://repository.apache.org/content/repositories/orgapachews-1043/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[VOTE] - Release Apache WSS4J 2.1.6

/wss4j/tags/wss4j-2.1.6/ Artifacts: https://repository.apache.org/content/repositories/orgapachews-1042/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

[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 collect

[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 lo

[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 lo

[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-SNAPS

[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-SNAPS

[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

[jira] [Resolved] (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 resolved WSS-577. - Resolution: Fixed > Binary compatibility broken between version <=2.1.3 and &

[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=15262484#comment-15262484 ] Colm O hEigeartaigh commented on WSS-577: - I added a copy of WSSecurityEngineResult back

[jira] [Updated] (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 updated WSS-577: Fix Version/s: 2.1.6 > Binary compatibility broken between version <=2.1.3 and &

[jira] [Closed] (WSS-576) No message with ID "SECURITY_ERROR" found in resource bundle

[ https://issues.apache.org/jira/browse/WSS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-576. --- Resolution: Not A Problem > No message with ID "SECURITY_ERROR" found in re

[jira] [Commented] (WSS-576) No message with ID "SECURITY_ERROR" found in resource bundle

[ https://issues.apache.org/jira/browse/WSS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251663#comment-15251663 ] Colm O hEigeartaigh commented on WSS-576: - You said that "we have flows where needs XML sec

[jira] [Commented] (WSS-576) No message with ID "SECURITY_ERROR" found in resource bundle

[ https://issues.apache.org/jira/browse/WSS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251573#comment-15251573 ] Colm O hEigeartaigh commented on WSS-576: - That won't work, WSSec.init() must be called before

[jira] [Commented] (WSS-576) No message with ID "SECURITY_ERROR" found in resource bundle

[ https://issues.apache.org/jira/browse/WSS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250987#comment-15250987 ] Colm O hEigeartaigh commented on WSS-576: - How are you instantiating WSS4J? These error messages

[jira] [Commented] (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:comment-tabpanel=15249664#comment-15249664 ] Colm O hEigeartaigh commented on WSS-575: - There is no ticket as far as I remember. CXF normally gets

[jira] [Resolved] (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 resolved WSS-575. - Resolution: Fixed > Support for Digest other than sha1 in xenc:EncryptionMet

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