[jira] [Commented] (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:comment-tabpanel=16804728#comment-16804728 ] Colm O hEigeartaigh commented on WSS-634: - Yep I'm planning to call a vote today. > Nodes are not

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

[ 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

[ 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

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

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

[ 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

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

[jira] [Commented] (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:comment-tabpanel=16769304#comment-16769304 ] Colm O hEigeartaigh commented on WSS-644: - Hi [~netmikey] actually I meant that you should try

[jira] [Commented] (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: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

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

[jira] [Updated] (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 updated WSS-644: Fix Version/s: 2.3.0 2.2.3 > Error when a SOAP-Fault is thrown with MTOM

[jira] [Resolved] (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 resolved WSS-643. - Resolution: Fixed > NullPointerException in getCacheManager >

[jira] [Updated] (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 updated WSS-643: Fix Version/s: 2.3.0 > NullPointerException in getCacheManager >

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

[ 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

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

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

[ 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

[ 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

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

[jira] [Updated] (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 updated WSS-642: Fix Version/s: 2.2.3 > Use LinkedHashSet instead of TreeSet within getInclusivePrefixes >

[jira] [Resolved] (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 resolved WSS-640. - Resolution: Fixed > Streaming Sender-Vouches validation does not work with SOAP 1.2 >

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

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

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

[ 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" method: > 

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

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

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

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

[jira] [Updated] (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 updated WSS-637: Fix Version/s: 2.3.0 > Refactor ReplayCache interface to use an expiry Instant instead of a

[jira] [Updated] (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 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

[ 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 instead of a

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

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

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

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

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

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

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

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

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

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

[ 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

[jira] [Resolved] (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 resolved WSS-634. - Resolution: Fixed > Nodes are not imported correctly when creating headers >

[jira] [Resolved] (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 resolved WSS-633. - Resolution: Fixed > Upgrade ErrorProne to support Java 11 >

[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: Attachment: wss4j-errorprone.patch > Upgrade ErrorProne to support Java 11 >

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

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

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

[jira] [Updated] (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 updated WSS-632: Attachment: 0001-WSS-632-An-initial-patch.patch > Support EhCache 3+ > -- > >

[jira] [Updated] (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 updated WSS-632: Fix Version/s: 2.3.0 > Support EhCache 3+ > -- > > Key:

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

Colm O hEigeartaigh created WSS-632: --- Summary: Support EhCache 3+ Key: WSS-632 URL: https://issues.apache.org/jira/browse/WSS-632 Project: WSS4J Issue Type: Task Reporter: Colm

[jira] [Resolved] (WSS-631) issue with wss4j message resource bundle.

[ https://issues.apache.org/jira/browse/WSS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-631. - Resolution: Not A Problem > issue with wss4j message resource bundle. >

[jira] [Commented] (WSS-631) issue with wss4j message resource bundle.

[ https://issues.apache.org/jira/browse/WSS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536954#comment-16536954 ] Colm O hEigeartaigh commented on WSS-631: - It looks like the openehealth classes are calling

[jira] [Commented] (WSS-631) issue with wss4j message resource bundle.

[ https://issues.apache.org/jira/browse/WSS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16533544#comment-16533544 ] Colm O hEigeartaigh commented on WSS-631: - Check to see if any of your code is calling

[jira] [Resolved] (WSS-630) Cannot find wss4j 2.2.2 inside maven repositories

[ https://issues.apache.org/jira/browse/WSS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-630. - Resolution: Fixed It's there now. > Cannot find wss4j 2.2.2 inside maven repositories >

[jira] [Closed] (WSS-630) Cannot find wss4j 2.2.2 inside maven repositories

[ https://issues.apache.org/jira/browse/WSS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-630. --- > Cannot find wss4j 2.2.2 inside maven repositories >

[jira] [Commented] (WSS-630) Cannot find wss4j 2.2.2 inside maven repositories

[ https://issues.apache.org/jira/browse/WSS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515543#comment-16515543 ] Colm O hEigeartaigh commented on WSS-630: - I'm just after releasing it, it will be there shortly :)

[jira] [Closed] (WSS-626) Duplicates in the PrefixList

[ https://issues.apache.org/jira/browse/WSS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-626. --- > Duplicates in the PrefixList > > > Key: WSS-626 >

[jira] [Closed] (WSS-625) Use RFC4648 base64 encoder for signature values and BST

[ https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-625. --- > Use RFC4648 base64 encoder for signature values and BST >

[jira] [Closed] (WSS-629) Support additional elements in SubjectConfirmationData

[ https://issues.apache.org/jira/browse/WSS-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-629. --- > Support additional elements in SubjectConfirmationData >

[jira] [Closed] (WSS-624) Support for SAAJ-RI 1.4.0

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

[jira] [Closed] (WSS-622) from SAMLCallback no possible setting SAML2 SubjectConfirmation.NameID

[ https://issues.apache.org/jira/browse/WSS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-622. --- > from SAMLCallback no possible setting SAML2 SubjectConfirmation.NameID >

[jira] [Closed] (WSS-627) Java 10 SAAJ support

[ https://issues.apache.org/jira/browse/WSS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-627. --- > Java 10 SAAJ support > > > Key: WSS-627 >

[jira] [Closed] (WSS-623) NameIdBean SPNameQualifier support

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

[jira] [Closed] (WSS-628) Support processing xop:Include for the streaming WS-Security stack

[ https://issues.apache.org/jira/browse/WSS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-628. --- > Support processing xop:Include for the streaming WS-Security stack >

[jira] [Commented] (XMLSCHEMA-52) Downloads page doesn't provide checksums or signatures

[ https://issues.apache.org/jira/browse/XMLSCHEMA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509844#comment-16509844 ] Colm O hEigeartaigh commented on XMLSCHEMA-52: -- [~dkulp] - can you close this JIRA? I

[jira] [Commented] (WSS-624) Support for SAAJ-RI 1.4.0

[ https://issues.apache.org/jira/browse/WSS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503144#comment-16503144 ] Colm O hEigeartaigh commented on WSS-624: - Some time next week I hope. > Support for SAAJ-RI 1.4.0

[jira] [Commented] (WSS-629) Support additional elements in SubjectConfirmationData

[ https://issues.apache.org/jira/browse/WSS-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494921#comment-16494921 ] Colm O hEigeartaigh commented on WSS-629: - Looks fine, but there are a few changes I'd like to see:

[jira] [Commented] (XMLSCHEMA-52) Downloads page doesn't provide checksums or signatures

[ https://issues.apache.org/jira/browse/XMLSCHEMA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16493316#comment-16493316 ] Colm O hEigeartaigh commented on XMLSCHEMA-52: -- It's fixed now - I added a download page

[jira] [Resolved] (WSS-628) Support processing xop:Include for the streaming WS-Security stack

[ https://issues.apache.org/jira/browse/WSS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-628. - Resolution: Fixed > Support processing xop:Include for the streaming WS-Security stack >

[jira] [Updated] (WSS-628) Support processing xop:Include for the streaming WS-Security stack

[ https://issues.apache.org/jira/browse/WSS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-628: Summary: Support processing xop:Include for the streaming WS-Security stack (was: Support

[jira] [Updated] (WSS-628) Support xop:Include for the streaming WS-Security stack

[ https://issues.apache.org/jira/browse/WSS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-628: Description: This task is to support xop:Include elements within CipherValue and

[jira] [Created] (WSS-628) Support xop:Include for the streaming WS-Security stack

Colm O hEigeartaigh created WSS-628: --- Summary: Support xop:Include for the streaming WS-Security stack Key: WSS-628 URL: https://issues.apache.org/jira/browse/WSS-628 Project: WSS4J Issue

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

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

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

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

[jira] [Resolved] (WSS-625) Use RFC4648 base64 encoder for signature values and BST

[ https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-625. - Resolution: Fixed > Use RFC4648 base64 encoder for signature values and BST >

[jira] [Updated] (WSS-625) Use RFC4648 base64 encoder for signature values and BST

[ https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-625: Fix Version/s: 2.2.2 > Use RFC4648 base64 encoder for signature values and BST >

[jira] [Resolved] (WSS-627) Java 10 SAAJ support

[ https://issues.apache.org/jira/browse/WSS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-627. - Resolution: Fixed > Java 10 SAAJ support > > > Key:

[jira] [Updated] (WSS-627) Java 10 SAAJ support

[ https://issues.apache.org/jira/browse/WSS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-627: Fix Version/s: 2.2.2 > Java 10 SAAJ support > > > Key:

[jira] [Created] (WSS-627) Java 10 SAAJ support

Colm O hEigeartaigh created WSS-627: --- Summary: Java 10 SAAJ support Key: WSS-627 URL: https://issues.apache.org/jira/browse/WSS-627 Project: WSS4J Issue Type: Improvement

[jira] [Resolved] (WSS-626) Duplicates in the PrefixList

[ https://issues.apache.org/jira/browse/WSS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-626. - Resolution: Fixed > Duplicates in the PrefixList > > >

[jira] [Updated] (WSS-626) Duplicates in the PrefixList

[ https://issues.apache.org/jira/browse/WSS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-626: Fix Version/s: 2.2.2 > Duplicates in the PrefixList > > >

[jira] [Commented] (WSS-626) Duplicates in the PrefixList

[ https://issues.apache.org/jira/browse/WSS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16413687#comment-16413687 ] Colm O hEigeartaigh commented on WSS-626: - I added a testcase based on the SOAP message you attached

[jira] [Commented] (WSS-625) Use RFC4648 base64 encoder for signature values and BST

[ https://issues.apache.org/jira/browse/WSS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380059#comment-16380059 ] Colm O hEigeartaigh commented on WSS-625: - The spec says that RFC-2045 should be used: "The

[jira] [Commented] (WSS-623) NameIdBean SPNameQualifier support

[ https://issues.apache.org/jira/browse/WSS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358265#comment-16358265 ] Colm O hEigeartaigh commented on WSS-623: - Thanks for the patch. > NameIdBean SPNameQualifier

[jira] [Updated] (WSS-623) NameIdBean SPNameQualifier support

[ https://issues.apache.org/jira/browse/WSS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-623: Fix Version/s: 2.2.2 2.1.13 > NameIdBean SPNameQualifier support >

[jira] [Resolved] (WSS-622) from SAMLCallback no possible setting SAML2 SubjectConfirmation.NameID

[ https://issues.apache.org/jira/browse/WSS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-622. - Resolution: Fixed > from SAMLCallback no possible setting SAML2 SubjectConfirmation.NameID

[jira] [Updated] (WSS-622) from SAMLCallback no possible setting SAML2 SubjectConfirmation.NameID

[ https://issues.apache.org/jira/browse/WSS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-622: Fix Version/s: 2.2.2 2.1.13 > from SAMLCallback no possible setting SAML2

[jira] [Commented] (WSS-623) NameIdBean SPNameQualifier support

[ https://issues.apache.org/jira/browse/WSS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357151#comment-16357151 ] Colm O hEigeartaigh commented on WSS-623: - Please submit a second PR for this issue, as I'm about to

[jira] [Commented] (WSS-622) from SAMLCallback no passible setting SAML2 SubjectConfirmation.NameID

[ https://issues.apache.org/jira/browse/WSS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355656#comment-16355656 ] Colm O hEigeartaigh commented on WSS-622: - You can set a SubjectBean object on the SAMLCallback and

[jira] [Closed] (WSS-621) Problem with TemplateGenerator

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

[jira] [Resolved] (WSS-621) Problem with TemplateGenerator

[ https://issues.apache.org/jira/browse/WSS-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-621. - Resolution: Won't Fix This JIRA is for Apache WSS4J and not XSS4J. > Problem with

[jira] [Created] (WSS-620) The SecurityTokenRefSTRParser should derive the key length from the DerivedKeyToken "Length" parameter

Colm O hEigeartaigh created WSS-620: --- Summary: The SecurityTokenRefSTRParser should derive the key length from the DerivedKeyToken "Length" parameter Key: WSS-620 URL:

[jira] [Resolved] (WSS-619) Support adding a custom KeyInfo Element for Signature

[ https://issues.apache.org/jira/browse/WSS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-619. - Resolution: Fixed > Support adding a custom KeyInfo Element for Signature >

[jira] [Created] (WSS-619) Support adding a custom KeyInfo Element for Signature

Colm O hEigeartaigh created WSS-619: --- Summary: Support adding a custom KeyInfo Element for Signature Key: WSS-619 URL: https://issues.apache.org/jira/browse/WSS-619 Project: WSS4J Issue

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

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-618. - Resolution: Fixed > Cannot create signature which includes KeyInfo >

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

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251797#comment-16251797 ] Colm O hEigeartaigh commented on WSS-618: - I've updated the code with a fix for the "action" case as

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

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reopened WSS-618: - > Cannot create signature which includes KeyInfo >

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

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-618. - Resolution: Fixed > Cannot create signature which includes KeyInfo >

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

[ https://issues.apache.org/jira/browse/WSS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251266#comment-16251266 ] Colm O hEigeartaigh commented on WSS-618: - OK I've fixed this for the DOM case only, by adding some

[jira] [Commented] (WSS-616) STRTransform TransformException when manually adding SAML Assertion via SAMLCallback.setAssertionElement()

[ https://issues.apache.org/jira/browse/WSS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209145#comment-16209145 ] Colm O hEigeartaigh commented on WSS-616: - I need more information on the scenario to reproduce the

[jira] [Closed] (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 closed WSS-586. --- > Don't query a CallbackHandler for a secret key when parsing a SAML Subject > for credentials >

[jira] [Closed] (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 closed WSS-599. --- > Upgrade to Java 8 DateTime API > -- > > Key: WSS-599 >

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

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

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

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

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

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

[jira] [Resolved] (WSS-614) org.apache.ws.security.transform.STRTransformProvider leak

[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-614. - Resolution: Workaround > org.apache.ws.security.transform.STRTransformProvider leak >

[jira] [Comment Edited] (WSS-614) org.apache.ws.security.transform.STRTransformProvider leak

[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143791#comment-16143791 ] Colm O hEigeartaigh edited comment on WSS-614 at 8/28/17 1:47 PM: -- No there

[jira] [Reopened] (WSS-614) org.apache.ws.security.transform.STRTransformProvider leak

[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reopened WSS-614: - > org.apache.ws.security.transform.STRTransformProvider leak >

[jira] [Resolved] (WSS-614) org.apache.ws.security.transform.STRTransformProvider leak

[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-614. - Resolution: Not A Problem > org.apache.ws.security.transform.STRTransformProvider leak >

[jira] [Commented] (WSS-614) org.apache.ws.security.transform.STRTransformProvider leak

[ https://issues.apache.org/jira/browse/WSS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16143728#comment-16143728 ] Colm O hEigeartaigh commented on WSS-614: - WSS4J has to add some security providers to work properly.

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