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

2020-01-03 Thread Colm O hEigeartaigh (Jira)
[ 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 gr

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

2020-01-03 Thread Colm O hEigeartaigh (Jira)
[ 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 gr

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

2020-01-03 Thread Colm O hEigeartaigh (Jira)
[ 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 sche

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

2020-01-02 Thread Colm O hEigeartaigh (Jira)
[ 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

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

2020-01-02 Thread Colm O hEigeartaigh (Jira)
[ 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

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

2020-01-02 Thread Colm O hEigeartaigh (Jira)
[ 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

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

2019-12-10 Thread Colm O hEigeartaigh (Jira)
[ 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

2019-11-25 Thread Colm O hEigeartaigh (Jira)
[ 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 QN

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

2019-11-06 Thread Colm O hEigeartaigh (Jira)
[ 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 tok

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

2019-11-06 Thread Colm O hEigeartaigh (Jira)
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

Re: Moving repos to git......

2019-11-01 Thread Colm O hEigeartaigh
Hi Dan, > 3) Once the code is there from SVN, we’ll need to update all the pom.xml’s > for the new locations and such on each of the active branches. > When will we have github mirrors that are synced to the new git repos? > > 4) I’m not sure yet what to do with the “parent” stuff or the

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

2019-10-23 Thread Colm O hEigeartaigh (Jira)
[ 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.

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

2019-10-22 Thread Colm O hEigeartaigh (Jira)
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

Re: Moving repos to git......

2019-10-21 Thread Colm O hEigeartaigh
+1 to moving Neethi, XML Schema and WSS4J to git. Colm. On Fri, Oct 18, 2019 at 5:14 PM Gary Gregory wrote: > FYI, over at Apache Commons, we've migrated most/all of our repositories > to GitBox and it's worked like a charm since, the integration with GitHub > is great. > > Gary > > On Fri,

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

2019-10-16 Thread Colm O hEigeartaigh (Jira)
[ 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 Signat

Re: xml-security with provider support

2019-10-16 Thread Colm O hEigeartaigh
Hi George, Yes, I added support here: https://issues.apache.org/jira/browse/WSS-656 Colm. On Wed, Oct 16, 2019 at 7:18 AM George Stanchev < george.stanc...@microfocus.com> wrote: > Hi, > > > > I noticed that recently Apache Santuario got support for crypto operations > with user-supplied JCE

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

2019-10-16 Thread Colm O hEigeartaigh (Jira)
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

Re: cxf client using StAX and ws-security policy fails in PolicyEnforcer when processing server response

2019-10-10 Thread Colm O hEigeartaigh
Hi Erik, Would it be possible instead to create a test-case that I can apply directly to CXF? Colm. On Fri, Sep 13, 2019 at 9:50 AM Erik Lund Jensen wrote: > Hi > > I have forked cxf and created a branch "feature/dispatcher-policy" where > the systests/jaxws DispatcherTest class has been

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

2019-10-08 Thread Colm O hEigeartaigh (Jira)
[ 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

2019-10-08 Thread Colm O hEigeartaigh (Jira)
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

2019-08-19 Thread Colm O hEigeartaigh (Jira)
[ 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 passw

Re: cxf client using StAX and ws-security policy fails in PolicyEnforcer when processing server response

2019-08-14 Thread Colm O hEigeartaigh
tedParts > at > org.apache.cxf.ws.policy.AssertionInfoMap.checkEffectivePolicy(AssertionInfoMap.java:179) > > If I remove the PolicyVerificationInInterceptor from the cxf chain then > the message is decrypted and everything looks fine. > Could it be, that the PolicyEnforcer needs to

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

2019-07-27 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-07-27 Thread Colm O hEigeartaigh (JIRA)
[ 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 requ

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

2019-07-27 Thread Colm O hEigeartaigh (JIRA)
[ 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 Envel

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

2019-07-27 Thread Colm O hEigeartaigh (JIRA)
[ 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 sche

Re: [VOTE] - Release Apache WSS4J 2.2.4

2019-07-27 Thread Colm O hEigeartaigh
With 5 +1 votes, including 3 binding +1 votes, this vote passes. I'll do the release. Colm. On Thu, Jul 25, 2019 at 12:37 PM Alessio Soldano wrote: > +1 > Thanks! > > On Sat, Jul 20, 2019 at 1:29 PM Colm O hEigeartaigh > wrote: > >> This is a vote to release Apache W

Re: [VOTE] - Release Apache WSS4J 2.2.4

2019-07-25 Thread Colm O hEigeartaigh
One more vote required here please... Colm. On Tue, Jul 23, 2019 at 7:42 PM Freeman Fang wrote: > +1 > - > Freeman(Yue) Fang > > Red Hat, Inc. > > > > > > On Jul 20, 2019, at 7:28 AM, Colm O hEigeartaigh > wrote: > > This is a vote to re

[VOTE] - Release Apache WSS4J 2.2.4

2019-07-20 Thread Colm O hEigeartaigh
-1070/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

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

2019-07-16 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-07-04 Thread Colm O hEigeartaigh (JIRA)
[ 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

2019-07-01 Thread Colm O hEigeartaigh (JIRA)
[ 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.:   [https

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

2019-06-27 Thread Colm O hEigeartaigh (JIRA)
[ 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 you

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

2019-06-27 Thread Colm O hEigeartaigh (JIRA)
[ 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 com

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

2019-06-27 Thread Colm O hEigeartaigh (JIRA)
[ 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

2019-06-27 Thread Colm O hEigeartaigh (JIRA)
[ 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

2019-06-12 Thread Colm O hEigeartaigh (JIRA)
[ 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 Hea

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

2019-06-12 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-05-31 Thread Colm O hEigeartaigh (JIRA)
[ 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 visi

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

2019-05-31 Thread Colm O hEigeartaigh (JIRA)
[ 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 visi

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

2019-05-31 Thread Colm O hEigeartaigh (JIRA)
[ 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 t

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

2019-05-23 Thread Colm O hEigeartaigh (JIRA)
[ 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 depende

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

2019-05-23 Thread Colm O hEigeartaigh (JIRA)
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

2019-05-14 Thread Colm O hEigeartaigh (JIRA)
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

2019-05-09 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-05-08 Thread Colm O hEigeartaigh (JIRA)
[ 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 >

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

2019-05-07 Thread Colm O hEigeartaigh (JIRA)
[ 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 requ

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

2019-05-07 Thread Colm O hEigeartaigh (JIRA)
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

2019-04-25 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-04-17 Thread Colm O hEigeartaigh (JIRA)
[ 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

2019-04-04 Thread Colm O hEigeartaigh (JIRA)
[ 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 head

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

2019-04-04 Thread Colm O hEigeartaigh (JIRA)
[ 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 constrai

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

2019-04-04 Thread Colm O hEigeartaigh (JIRA)
[ 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 enab

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

2019-04-04 Thread Colm O hEigeartaigh (JIRA)
[ 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

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

2019-04-04 Thread Colm O hEigeartaigh (JIRA)
[ 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 getInclusivePrefi

Re: [VOTE] - Release Apache WSS4J 2.2.3

2019-04-04 Thread Colm O hEigeartaigh
With 3 binding +1 votes, and one non-binding +1 vote, this vote passes. I'll do the release. Colm. On Thu, Apr 4, 2019 at 2:10 PM Alessio Soldano wrote: > +1 > > Thanks > > On Fri, Mar 29, 2019 at 6:50 PM Colm O hEigeartaigh > wrote: > >> This is a vote to

[VOTE] - Release Apache WSS4J 2.2.3

2019-03-29 Thread Colm O hEigeartaigh
-1069/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

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

2019-03-29 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804728#comment-16804728 ] Colm O hEigeartaigh commented on WSS-634: - Yep I'm planning to call a vote today. > No

[jira] [Commented] (WSS-645) using WSS4j to genrate WS-SecurityPolicy without CXF

2019-03-13 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791647#comment-16791647 ] Colm O hEigeartaigh commented on WSS-645: - Yes, CXF parses the policy and configures WSS4J

[jira] [Commented] (WSS-645) using WSS4j to genrate WS-SecurityPolicy without CXF

2019-03-07 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787256#comment-16787256 ] Colm O hEigeartaigh commented on WSS-645: - You could look at the streaming WS-SecurityPolicy tests

[jira] [Resolved] (WSS-645) using WSS4j to genrate WS-SecurityPolicy without CXF

2019-03-07 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-645. - Resolution: Won't Fix > using WSS4j to genrate WS-SecurityPolicy without

[jira] [Commented] (WSS-645) using WSS4j to genrate WS-SecurityPolicy without CXF

2019-03-07 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786846#comment-16786846 ] Colm O hEigeartaigh commented on WSS-645: - The WS-SecurityPolicy implementation was historically

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

2019-02-18 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770985#comment-16770985 ] Colm O hEigeartaigh commented on WSS-644: - OK great, thanks for checking. > Error when a SOAP-Fa

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

2019-02-15 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769304#comment-16769304 ] Colm O hEigeartaigh commented on WSS-644: - Hi [~netmikey] actually I meant that you should try 2.2.3

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

2019-02-15 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769265#comment-16769265 ] Colm O hEigeartaigh commented on WSS-644: - [~netmikey] - I've deployed a new SNAPSHOT to the apache

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

2019-02-14 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-644. - Resolution: Fixed This issue was solved for the "English" case he

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

2019-02-14 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-644: Fix Version/s: 2.3.0 2.2.3 > Error when a SOAP-Fault is thrown with M

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

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-643. - Resolution: Fixed > NullPointerException in getCacheMana

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

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-643: Fix Version/s: 2.3.0 > NullPointerException in getCacheMana

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

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756255#comment-16756255 ] Colm O hEigeartaigh commented on WSS-643: - See my comment on the CXF JIRA. I'll fix the NPE in WSS4J

[jira] [Commented] (WSS-638) out of memory when validating XML-Signature of an encypted SOAP-Message with large attachment

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756248#comment-16756248 ] Colm O hEigeartaigh commented on WSS-638: - [~mhaeusle] - would you consider submitting a patch

[jira] [Comment Edited] (WSS-643) NullPointerException in getCacheManager

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756193#comment-16756193 ] Colm O hEigeartaigh edited comment on WSS-643 at 1/30/19 2:56 PM: -- Are you

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

2019-01-30 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756193#comment-16756193 ] Colm O hEigeartaigh commented on WSS-643: - Are you doing any kind of custom ehcache configuration

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

2019-01-29 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754784#comment-16754784 ] Colm O hEigeartaigh commented on WSS-634: - I'm thinking of releasing in about a month. I want

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

2019-01-28 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-642: Fix Version/s: 2.2.3 > Use LinkedHashSet instead of TreeSet within getInclusivePrefi

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

2019-01-21 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-640. - Resolution: Fixed > Streaming Sender-Vouches validation does not work with SOAP

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

2019-01-21 Thread Colm O hEigeartaigh (JIRA)
Colm O hEigeartaigh created WSS-640: --- Summary: Streaming Sender-Vouches validation does not work with SOAP 1.2 Key: WSS-640 URL: https://issues.apache.org/jira/browse/WSS-640 Project: WSS4J

Re: [VOTE] Release Apache Axiom 1.2.22

2019-01-14 Thread Colm O hEigeartaigh
- > To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org > For additional commands, e-mail: dev-h...@ws.apache.org > > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://ta

[jira] [Commented] (WSS-639) IssueInstant NotOnOrAfter is not checked when specified

2018-12-19 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725431#comment-16725431 ] Colm O hEigeartaigh commented on WSS-639: - validTill is checked in the "checkConditions&qu

[jira] [Resolved] (WSS-639) IssueInstant NotOnOrAfter is not checked when specified

2018-12-19 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-639. - Resolution: Not A Problem > IssueInstant NotOnOrAfter is not checked when specif

[jira] [Closed] (XMLSCHEMA-53) Illegal reflective access by org.apache.ws.commons.schema.utils.DOMUtil

2018-12-10 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/XMLSCHEMA-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed XMLSCHEMA-53. > Illegal reflective access by org.apache.ws.commons.schema.utils.DOMU

Re: [VOTE] - Release Apache XMLSchema 2.2.4

2018-12-10 Thread Colm O hEigeartaigh
Freeman Fang > wrote: > >> > >> +1 > >> > >> Thanks! > >> - > >> Freeman(Yue) Fang > >> > >> Red Hat, Inc. > >> > >> > >> > >> > >> > >> On Dec 4, 2018, at 7:56 PM, C

[VOTE] - Release Apache XMLSchema 2.2.4

2018-12-04 Thread Colm O hEigeartaigh
-1066/ +1 from me. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

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

2018-11-28 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-637: Fix Version/s: 2.3.0 > Refactor ReplayCache interface to use an expiry Instant inst

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

2018-11-28 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-637: Summary: Refactor ReplayCache interface to use an expiry Instant instead of a long TTL value

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

2018-11-28 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-637. - Resolution: Fixed > Refactor ReplayCache interface to use an expirty Instant inst

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

2018-11-28 Thread Colm O hEigeartaigh (JIRA)
Colm O hEigeartaigh created WSS-637: --- Summary: Refactor ReplayCache interface to use an expirty Instant instead of a long TTL value Key: WSS-637 URL: https://issues.apache.org/jira/browse/WSS-637

[jira] [Closed] (WSS-636) CLONE - Password set to null in UsernameTokenValidator

2018-11-20 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-636. --- Resolution: Won't Fix > CLONE - Password set to null in UsernameTokenValida

[jira] [Commented] (WSS-636) CLONE - Password set to null in UsernameTokenValidator

2018-11-20 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16693534#comment-16693534 ] Colm O hEigeartaigh commented on WSS-636: - The UsernameTokenValidator is designed to be used

[jira] [Closed] (WSS-636) CLONE - Password set to null in UsernameTokenValidator

2018-11-20 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-636. --- Resolution: Duplicate > CLONE - Password set to null in UsernameTokenValida

[jira] [Resolved] (WSS-635) verifyPlaintextPassword bug that can't validate #PasswordText type of plain password

2018-11-16 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-635. - Resolution: Not A Problem > verifyPlaintextPassword bug that can't validate #PasswordT

[jira] [Commented] (WSS-635) verifyPlaintextPassword bug that can't validate #PasswordText type of plain password

2018-11-16 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689252#comment-16689252 ] Colm O hEigeartaigh commented on WSS-635: - The logic in verifyDigestPassword works for both

Re: [VOTE] Release Apache Axiom 1.2.21 (take 2)

2018-11-05 Thread Colm O hEigeartaigh
g > For additional commands, e-mail: dev-h...@ws.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

Re: [VOTE] Release Apache Axiom 1.2.21

2018-10-30 Thread Colm O hEigeartaigh
onal commands, e-mail: dev-h...@ws.apache.org > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

Re: [VOTE] Release Apache WS parent POM 3

2018-10-24 Thread Colm O hEigeartaigh
e.org > For additional commands, e-mail: dev-h...@ws.apache.org > > > -- > Daniel Kulp > dk...@apache.org - http://dankulp.com/blog > Talend Community Coder - http://talend.com <http://coders.talend.com> > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com

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

2018-10-18 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-634. - Resolution: Fixed > Nodes are not imported correctly when creating head

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

2018-10-15 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-633. - Resolution: Fixed > Upgrade ErrorProne to support Java

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

2018-10-01 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-633: Attachment: wss4j-errorprone.patch > Upgrade ErrorProne to support Java

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

2018-10-01 Thread Colm O hEigeartaigh (JIRA)
Colm O hEigeartaigh created WSS-633: --- Summary: Upgrade ErrorProne to support Java 11 Key: WSS-633 URL: https://issues.apache.org/jira/browse/WSS-633 Project: WSS4J Issue Type: Task

[jira] [Commented] (WSS-456) Not possible to support SymmetricBinding ProtectTokens policy

2018-08-31 Thread Colm O hEigeartaigh (JIRA)
[ https://issues.apache.org/jira/browse/WSS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598640#comment-16598640 ] Colm O hEigeartaigh commented on WSS-456: - ProtectTokens + SymmericBinding is actually supported

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