[jira] [Resolved] (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:all-tabpanel ] Colm O hEigeartaigh resolved WSS-674. - Resolution: Not A Problem > How to get WSS4j 2.3.0 jar > -- > >

[jira] [Closed] (WSS-668) Rename WSSConstants ENCRYPT actions

[ https://issues.apache.org/jira/browse/WSS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-668. --- > Rename WSSConstants ENCRYPT actions > --- > >

[jira] [Closed] (WSS-637) Refactor ReplayCache interface to use an expiry Instant instead of a long TTL value

[ https://issues.apache.org/jira/browse/WSS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-637. --- > Refactor ReplayCache interface to use an expiry Instant instead of a long TTL > value >

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

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

[jira] [Closed] (WSS-669) Rename ConfigurationConstants ENCRYPT actions

[ https://issues.apache.org/jira/browse/WSS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-669. --- > Rename ConfigurationConstants ENCRYPT actions > - > >

[jira] [Resolved] (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 resolved WSS-673. - Resolution: Fixed > Using default Java Security and Merlin is very slow for PKCS12 >

[jira] [Commented] (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:comment-tabpanel=17128047#comment-17128047 ] Colm O hEigeartaigh commented on WSS-673: - For the record, this will default to false for WSS4J

[jira] [Updated] (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 updated WSS-673: Fix Version/s: 2.2.6 > Using default Java Security and Merlin is very slow for PKCS12 >

[jira] [Commented] (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:comment-tabpanel=17126849#comment-17126849 ] Colm O hEigeartaigh commented on WSS-673: - Yes definitely for 2.3.0. I'll backport it for 2.2.X, but

[jira] [Commented] (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:comment-tabpanel=17126486#comment-17126486 ] Colm O hEigeartaigh commented on WSS-673: - [~jjathman] - I've submitted a pull request for this,

[jira] [Updated] (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 updated WSS-673: Fix Version/s: 2.3.0 > Using default Java Security and Merlin is very slow for PKCS12 >

[jira] [Commented] (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:comment-tabpanel=17119351#comment-17119351 ] Colm O hEigeartaigh commented on WSS-673: - How are you configuring WSS4J? > Using default Java

[jira] [Resolved] (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 resolved WSS-672. - Resolution: Fixed > Make sure to process all elements of the SAML Signature KeyInfo >

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

Colm O hEigeartaigh created WSS-672: --- Summary: Make sure to process all elements of the SAML Signature KeyInfo Key: WSS-672 URL: https://issues.apache.org/jira/browse/WSS-672 Project: WSS4J

[jira] [Commented] (WSS-671) AttachmentId issue

[ https://issues.apache.org/jira/browse/WSS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101500#comment-17101500 ] Colm O hEigeartaigh commented on WSS-671: - The URL Decoding was added for this JIRA:

[jira] [Comment Edited] (WSS-671) AttachmentId issue

[ https://issues.apache.org/jira/browse/WSS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100885#comment-17100885 ] Colm O hEigeartaigh edited comment on WSS-671 at 5/6/20, 3:18 PM: -- I don't

[jira] [Commented] (WSS-671) AttachmentId issue

[ https://issues.apache.org/jira/browse/WSS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100885#comment-17100885 ] Colm O hEigeartaigh commented on WSS-671: - I don't think WSS4J does any URL Decoding on XOP

[jira] [Resolved] (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 resolved WSS-670. - Resolution: Fixed Thanks for the PR. > Expected signature algorithm is overwriten with

[jira] [Updated] (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 updated WSS-670: Fix Version/s: 2.2.6 2.3.0 > Expected signature algorithm is overwriten

[jira] [Resolved] (WSS-668) Rename WSSConstants ENCRYPT actions

[ https://issues.apache.org/jira/browse/WSS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-668. - Resolution: Fixed > Rename WSSConstants ENCRYPT actions >

[jira] [Resolved] (WSS-669) Rename ConfigurationConstants ENCRYPT actions

[ https://issues.apache.org/jira/browse/WSS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-669. - Resolution: Fixed > Rename ConfigurationConstants ENCRYPT actions >

[jira] [Created] (WSS-669) Rename ConfigurationConstants ENCRYPT actions

Colm O hEigeartaigh created WSS-669: --- Summary: Rename ConfigurationConstants ENCRYPT actions Key: WSS-669 URL: https://issues.apache.org/jira/browse/WSS-669 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-632) Support EhCache 3+

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

[jira] [Resolved] (WSS-662) [OSGi] Support for SAAJ-RI 1.4.0

[ https://issues.apache.org/jira/browse/WSS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-662. - Resolution: Fixed > [OSGi] Support for SAAJ-RI 1.4.0 > > >

[jira] [Updated] (WSS-662) [OSGi] Support for SAAJ-RI 1.4.0

[ https://issues.apache.org/jira/browse/WSS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-662: Fix Version/s: 2.3.0 > [OSGi] Support for SAAJ-RI 1.4.0 > >

[jira] [Resolved] (WSS-667) Support JDK14

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

[jira] [Created] (WSS-667) Support JDK14

Colm O hEigeartaigh created WSS-667: --- Summary: Support JDK14 Key: WSS-667 URL: https://issues.apache.org/jira/browse/WSS-667 Project: WSS4J Issue Type: Improvement Reporter:

[jira] [Closed] (WSS-663) Missing ECC key support

[ https://issues.apache.org/jira/browse/WSS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-663. --- > Missing ECC key support > --- > > Key: WSS-663 >

[jira] [Closed] (WSS-653) Better diagnostics for null password

[ https://issues.apache.org/jira/browse/WSS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-653. --- > Better diagnostics for null password > > >

[jira] [Closed] (WSS-666) Support processing SignatureValue bytes stored in attachments

[ https://issues.apache.org/jira/browse/WSS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-666. --- > Support processing SignatureValue bytes stored in attachments >

[jira] [Closed] (WSS-659) SecurityContextToken validator set by wrong QName

[ https://issues.apache.org/jira/browse/WSS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-659. --- > SecurityContextToken validator set by wrong QName >

[jira] [Closed] (WSS-665) Add cryptacular dependency and upgrade to 1.2.4 to fix CVE-2020-7226

[ https://issues.apache.org/jira/browse/WSS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-665. --- > Add cryptacular dependency and upgrade to 1.2.4 to fix CVE-2020-7226 >

[jira] [Closed] (WSS-658) Enable signature confirmation for signed SAML tokens

[ https://issues.apache.org/jira/browse/WSS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-658. --- > Enable signature confirmation for signed SAML tokens >

[jira] [Closed] (WSS-656) Add the ability to specify a security Provider to use with Signature

[ https://issues.apache.org/jira/browse/WSS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-656. --- > Add the ability to specify a security Provider to use with Signature >

[jira] [Resolved] (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:all-tabpanel ] Colm O hEigeartaigh resolved WSS-581. - Resolution: Cannot Reproduce Please supply a test-case and then it can be re-opened. >

[jira] [Resolved] (WSS-666) Support processing SignatureValue bytes stored in attachments

[ https://issues.apache.org/jira/browse/WSS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-666. - Resolution: Fixed > Support processing SignatureValue bytes stored in attachments >

[jira] [Updated] (WSS-666) Support processing SignatureValue bytes stored in attachments

[ https://issues.apache.org/jira/browse/WSS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-666: Fix Version/s: 2.2.5 > Support processing SignatureValue bytes stored in attachments >

[jira] [Created] (WSS-666) Support processing SignatureValue bytes stored in attachments

Colm O hEigeartaigh created WSS-666: --- Summary: Support processing SignatureValue bytes stored in attachments Key: WSS-666 URL: https://issues.apache.org/jira/browse/WSS-666 Project: WSS4J

[jira] [Closed] (WSS-664) Problem using IBM JDK

[ https://issues.apache.org/jira/browse/WSS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-664. --- > Problem using IBM JDK > - > > Key: WSS-664 >

[jira] [Resolved] (WSS-664) Problem using IBM JDK

[ https://issues.apache.org/jira/browse/WSS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-664. - Resolution: Not A Problem > Problem using IBM JDK > - > >

[jira] [Commented] (WSS-664) Problem using IBM JDK

[ https://issues.apache.org/jira/browse/WSS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17039942#comment-17039942 ] Colm O hEigeartaigh commented on WSS-664: - I can build the WSS4J master source fine using this JDK:

[jira] [Resolved] (WSS-665) Add cryptacular dependency and upgrade to 1.2.4 to fix CVE-2020-7226

[ https://issues.apache.org/jira/browse/WSS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-665. - Resolution: Fixed > Add cryptacular dependency and upgrade to 1.2.4 to fix CVE-2020-7226 >

[jira] [Commented] (WSS-664) Problem using IBM JDK

[ https://issues.apache.org/jira/browse/WSS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17036945#comment-17036945 ] Colm O hEigeartaigh commented on WSS-664: - What actual IBM JDK are you using (and where can I

[jira] [Resolved] (WSS-663) Missing ECC key support

[ https://issues.apache.org/jira/browse/WSS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-663. - Resolution: Fixed > Missing ECC key support > --- > >

[jira] [Updated] (WSS-663) Missing ECC key support

[ https://issues.apache.org/jira/browse/WSS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-663: Fix Version/s: 2.2.5 2.3.0 > Missing ECC key support >

[jira] [Resolved] (WSS-661) Change BouncyCastle provider registering

[ https://issues.apache.org/jira/browse/WSS-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-661. - Resolution: Fixed > Change BouncyCastle provider registering >

[jira] [Created] (WSS-661) Change BouncyCastle provider registering

Colm O hEigeartaigh created WSS-661: --- Summary: Change BouncyCastle provider registering Key: WSS-661 URL: https://issues.apache.org/jira/browse/WSS-661 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-659) SecurityContextToken validator set by wrong QName

[ https://issues.apache.org/jira/browse/WSS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-659. - Resolution: Fixed > SecurityContextToken validator set by wrong QName >

[jira] [Updated] (WSS-659) SecurityContextToken validator set by wrong QName

[ https://issues.apache.org/jira/browse/WSS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-659: Fix Version/s: 2.1.13 > SecurityContextToken validator set by wrong QName >

[jira] [Updated] (WSS-659) SecurityContextToken validator set by wrong QName

[ https://issues.apache.org/jira/browse/WSS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-659: Fix Version/s: 2.3.0 > SecurityContextToken validator set by wrong QName >

[jira] [Closed] (XMLSCHEMA-58) Schema version not set

[ https://issues.apache.org/jira/browse/XMLSCHEMA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed XMLSCHEMA-58. > Schema version not set > -- > > Key:

[jira] [Closed] (XMLSCHEMA-51) Problem with included schemas with attribute group references

[ https://issues.apache.org/jira/browse/XMLSCHEMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed XMLSCHEMA-51. > Problem with included schemas with attribute group references >

[jira] [Closed] (XMLSCHEMA-56) Element defined in a base type sometimes isn't visited by an XmlSchemaWalker's visitor

[ https://issues.apache.org/jira/browse/XMLSCHEMA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed XMLSCHEMA-56. > Element defined in a base type sometimes isn't visited by an > XmlSchemaWalker's

[jira] [Resolved] (XMLSCHEMA-51) Problem with included schemas with attribute group references

[ https://issues.apache.org/jira/browse/XMLSCHEMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved XMLSCHEMA-51. -- Resolution: Fixed > Problem with included schemas with attribute group

[jira] [Updated] (XMLSCHEMA-51) Problem with included schemas with attribute group references

[ https://issues.apache.org/jira/browse/XMLSCHEMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated XMLSCHEMA-51: - Fix Version/s: 2.2.5 > Problem with included schemas with attribute group

[jira] [Assigned] (XMLSCHEMA-51) Problem with included schemas with attribute group references

[ https://issues.apache.org/jira/browse/XMLSCHEMA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned XMLSCHEMA-51: Assignee: Colm O hEigeartaigh > Problem with included schemas with

[jira] [Resolved] (XMLSCHEMA-58) Schema version not set

[ https://issues.apache.org/jira/browse/XMLSCHEMA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved XMLSCHEMA-58. -- Resolution: Fixed > Schema version not set > -- > >

[jira] [Updated] (XMLSCHEMA-58) Schema version not set

[ https://issues.apache.org/jira/browse/XMLSCHEMA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated XMLSCHEMA-58: - Fix Version/s: 2.2.5 > Schema version not set > -- > >

[jira] [Assigned] (XMLSCHEMA-58) Schema version not set

[ https://issues.apache.org/jira/browse/XMLSCHEMA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned XMLSCHEMA-58: Assignee: Colm O hEigeartaigh > Schema version not set >

[jira] [Commented] (XMLSCHEMA-58) Schema version not set

[ https://issues.apache.org/jira/browse/XMLSCHEMA-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992386#comment-16992386 ] Colm O hEigeartaigh commented on XMLSCHEMA-58: -- Please consider submitting a pull request

[jira] [Updated] (WSS-659) SecurityContextToken validator set by wrong QName

[ https://issues.apache.org/jira/browse/WSS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-659: Fix Version/s: 2.2.5 > SecurityContextToken validator set by wrong QName >

[jira] [Resolved] (WSS-658) Enable signature confirmation for signed SAML tokens

[ https://issues.apache.org/jira/browse/WSS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-658. - Resolution: Fixed > Enable signature confirmation for signed SAML tokens >

[jira] [Created] (WSS-658) Enable signature confirmation for signed SAML tokens

Colm O hEigeartaigh created WSS-658: --- Summary: Enable signature confirmation for signed SAML tokens Key: WSS-658 URL: https://issues.apache.org/jira/browse/WSS-658 Project: WSS4J Issue

[jira] [Resolved] (WSS-657) Update OpenSAML Dependency to 3.4.x

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

[jira] [Created] (WSS-657) Update OpenSAML Dependency to 3.4.x

Colm O hEigeartaigh created WSS-657: --- Summary: Update OpenSAML Dependency to 3.4.x Key: WSS-657 URL: https://issues.apache.org/jira/browse/WSS-657 Project: WSS4J Issue Type: Improvement

[jira] [Resolved] (WSS-656) Add the ability to specify a security Provider to use with Signature

[ https://issues.apache.org/jira/browse/WSS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-656. - Resolution: Fixed > Add the ability to specify a security Provider to use with Signature >

[jira] [Created] (WSS-656) Add the ability to specify a security Provider to use with Signature

Colm O hEigeartaigh created WSS-656: --- Summary: Add the ability to specify a security Provider to use with Signature Key: WSS-656 URL: https://issues.apache.org/jira/browse/WSS-656 Project: WSS4J

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

[ https://issues.apache.org/jira/browse/WSS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-655: Description: WSS4J currently only supports streaming WS-Security MTOM on the inbound side,

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

Colm O hEigeartaigh created WSS-655: --- Summary: Support outbound Streaming WS-Security MTOM Key: WSS-655 URL: https://issues.apache.org/jira/browse/WSS-655 Project: WSS4J Issue Type:

[jira] [Updated] (WSS-653) Better diagnostics for null password

[ https://issues.apache.org/jira/browse/WSS-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-653: Fix Version/s: 2.2.5 > Better diagnostics for null password >

[jira] [Closed] (WSS-633) Upgrade ErrorProne to support Java 11

[ https://issues.apache.org/jira/browse/WSS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-633. --- > Upgrade ErrorProne to support Java 11 > - > >

[jira] [Closed] (WSS-648) Performance problem with very big request

[ https://issues.apache.org/jira/browse/WSS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-648. --- > Performance problem with very big request > - > >

[jira] [Closed] (WSS-651) Incorrect signature if document has WSU_NS declared on SOAP Header or Envelope

[ https://issues.apache.org/jira/browse/WSS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-651. --- > Incorrect signature if document has WSU_NS declared on SOAP Header or Envelope >

[jira] [Closed] (WSS-649) Remove Doctypes from the streaming schemas

[ https://issues.apache.org/jira/browse/WSS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-649. --- > Remove Doctypes from the streaming schemas > -- > >

[jira] [Updated] (WSS-633) Upgrade ErrorProne to support Java 11

[ https://issues.apache.org/jira/browse/WSS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-633: Fix Version/s: 2.2.4 > Upgrade ErrorProne to support Java 11 >

[jira] [Commented] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878390#comment-16878390 ] Colm O hEigeartaigh commented on WSS-652: - Thanks for checking [~netmikey] I'll get a release out

[jira] [Commented] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876016#comment-16876016 ] Colm O hEigeartaigh commented on WSS-652: - Yes, I just deployed a new SNAPSHOT, e.g.:  

[jira] [Resolved] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-652. - Resolution: Fixed Please test with a WSS4J 2.2.4-SNAPSHOT jar and see if it's fixed for

[jira] [Updated] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-652: Fix Version/s: 2.2.4 2.3.0 > MTOM Content-Id handling doesn't comply with

[jira] [Commented] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873940#comment-16873940 ] Colm O hEigeartaigh commented on WSS-652: - I moved this issue to WSS4J, as that's where the problem

[jira] [Moved] (WSS-652) MTOM Content-Id handling doesn't comply with RFC2392: .NET issues

[ https://issues.apache.org/jira/browse/WSS-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh moved CXF-8061 to WSS-652: -- Estimated Complexity: (was: Unknown) Affects Version/s:

[jira] [Resolved] (WSS-651) Incorrect signature if document has WSU_NS declared on SOAP Header or Envelope

[ https://issues.apache.org/jira/browse/WSS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-651. - Resolution: Fixed > Incorrect signature if document has WSU_NS declared on SOAP Header or

[jira] [Updated] (WSS-651) Incorrect signature if document has WSU_NS declared on SOAP Header or Envelope

[ https://issues.apache.org/jira/browse/WSS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-651: Fix Version/s: 2.2.4 2.3.0 > Incorrect signature if document has WSU_NS

[jira] [Resolved] (XMLSCHEMA-56) Element defined in a base type sometimes isn't visited by an XmlSchemaWalker's visitor

[ https://issues.apache.org/jira/browse/XMLSCHEMA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved XMLSCHEMA-56. -- Resolution: Fixed > Element defined in a base type sometimes isn't visited

[jira] [Updated] (XMLSCHEMA-56) Element defined in a base type sometimes isn't visited by an XmlSchemaWalker's visitor

[ https://issues.apache.org/jira/browse/XMLSCHEMA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated XMLSCHEMA-56: - Fix Version/s: 2.2.5 > Element defined in a base type sometimes isn't visited

[jira] [Assigned] (XMLSCHEMA-56) Element defined in a base type sometimes isn't visited by an XmlSchemaWalker's visitor

[ https://issues.apache.org/jira/browse/XMLSCHEMA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned XMLSCHEMA-56: Assignee: Colm O hEigeartaigh > Element defined in a base type

[jira] [Resolved] (WSS-650) Exclude guava 19.0 dependency

[ https://issues.apache.org/jira/browse/WSS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-650. - Resolution: Fixed > Exclude guava 19.0 dependency > - > >

[jira] [Created] (WSS-650) Exclude guava 19.0 dependency

Colm O hEigeartaigh created WSS-650: --- Summary: Exclude guava 19.0 dependency Key: WSS-650 URL: https://issues.apache.org/jira/browse/WSS-650 Project: WSS4J Issue Type: Improvement

[jira] [Created] (WSS-649) Remove Doctypes from the streaming schemas

Colm O hEigeartaigh created WSS-649: --- Summary: Remove Doctypes from the streaming schemas Key: WSS-649 URL: https://issues.apache.org/jira/browse/WSS-649 Project: WSS4J Issue Type: Task

[jira] [Commented] (XMLSCHEMA-56) Element defined in a base type sometimes isn't visited by an XmlSchemaWalker's visitor

[ https://issues.apache.org/jira/browse/XMLSCHEMA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836207#comment-16836207 ] Colm O hEigeartaigh commented on XMLSCHEMA-56: -- Could you submit a pull request for this

[jira] [Deleted] (NEETHI-20) neethi

[ https://issues.apache.org/jira/browse/NEETHI-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh deleted NEETHI-20: -- > neethi > -- > > Key: NEETHI-20 > URL:

[jira] [Resolved] (WSS-648) Performance problem with very big request

[ https://issues.apache.org/jira/browse/WSS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-648. - Resolution: Fixed > Performance problem with very big request >

[jira] [Created] (WSS-648) Performance problem with very big request

Colm O hEigeartaigh created WSS-648: --- Summary: Performance problem with very big request Key: WSS-648 URL: https://issues.apache.org/jira/browse/WSS-648 Project: WSS4J Issue Type: Bug

[jira] [Resolved] (WSS-647) WSS4J trunk build is failing due to expired certificates

[ https://issues.apache.org/jira/browse/WSS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-647. - Resolution: Fixed Thanks for reporting, it's fixed now. > WSS4J trunk build is failing due

[jira] [Resolved] (WSS-646) Windows Server 2019 support

[ https://issues.apache.org/jira/browse/WSS-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-646. - Resolution: Not A Problem Please don't create JIRAs to ask questions, ask the user mailing

[jira] [Closed] (WSS-634) Nodes are not imported correctly when creating headers

[ https://issues.apache.org/jira/browse/WSS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-634. --- > Nodes are not imported correctly when creating headers >

[jira] [Closed] (WSS-641) Add the ability to configure a different separator for certificate constraints

[ https://issues.apache.org/jira/browse/WSS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-641. --- > Add the ability to configure a different separator for certificate constraints >

[jira] [Closed] (WSS-644) Error when a SOAP-Fault is thrown with MTOM enabled

[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-644. --- > Error when a SOAP-Fault is thrown with MTOM enabled >

[jira] [Closed] (WSS-640) Streaming Sender-Vouches validation does not work with SOAP 1.2

[ https://issues.apache.org/jira/browse/WSS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-640. --- > Streaming Sender-Vouches validation does not work with SOAP 1.2 >

[jira] [Closed] (WSS-642) Use LinkedHashSet instead of TreeSet within getInclusivePrefixes

[ https://issues.apache.org/jira/browse/WSS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-642. --- > Use LinkedHashSet instead of TreeSet within getInclusivePrefixes >

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