[jira] [Resolved] (WSS-427) Add support for processing UsernameToken Created Dates

[ https://issues.apache.org/jira/browse/WSS-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-427. - Resolution: Fixed Add support for processing UsernameToken Created Dates

[jira] [Commented] (WSS-363) Support pluggable Validation of received tokens as per DOM code

[ https://issues.apache.org/jira/browse/WSS-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13587812#comment-13587812 ] Colm O hEigeartaigh commented on WSS-363: - Hi Marc, One feature that is missing in

[jira] [Created] (WSS-426) Support future TTL in the StaX code for Timestamps

Colm O hEigeartaigh created WSS-426: --- Summary: Support future TTL in the StaX code for Timestamps Key: WSS-426 URL: https://issues.apache.org/jira/browse/WSS-426 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-426) Support future TTL in the StaX code for Timestamps

[ https://issues.apache.org/jira/browse/WSS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-426. - Resolution: Fixed Support future TTL in the StaX code for Timestamps

[jira] [Resolved] (WSS-420) Add the ability to explicitly allow/disallow UsernameTokens with no passwords

[ https://issues.apache.org/jira/browse/WSS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-420. - Resolution: Fixed Add the ability to explicitly allow/disallow UsernameTokens with no

[jira] [Updated] (WSS-350) Update package names

[ https://issues.apache.org/jira/browse/WSS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-350: Description: The swssf branch currently uses org.swssf, WSS4J currently uses

[jira] [Resolved] (WSS-350) Update package names

[ https://issues.apache.org/jira/browse/WSS-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-350. - Resolution: Fixed Update package names Key:

[jira] [Created] (WSS-425) Add + update OSGi import/export information in the new modules

Colm O hEigeartaigh created WSS-425: --- Summary: Add + update OSGi import/export information in the new modules Key: WSS-425 URL: https://issues.apache.org/jira/browse/WSS-425 Project: WSS4J

[jira] [Resolved] (WSS-373) Check sender-vouches and holder-of-key requirements for SAML tokens.

[ https://issues.apache.org/jira/browse/WSS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-373. - Resolution: Fixed Check sender-vouches and holder-of-key requirements for SAML tokens.

[jira] [Created] (WSS-424) Signature Element is not inserted in the correct place in the header in certain circumstances

Colm O hEigeartaigh created WSS-424: --- Summary: Signature Element is not inserted in the correct place in the header in certain circumstances Key: WSS-424 URL: https://issues.apache.org/jira/browse/WSS-424

[jira] [Created] (WSS-423) Suuport CRL checking for streaming code

Colm O hEigeartaigh created WSS-423: --- Summary: Suuport CRL checking for streaming code Key: WSS-423 URL: https://issues.apache.org/jira/browse/WSS-423 Project: WSS4J Issue Type: Bug

[jira] [Updated] (WSS-423) Support CRL checking for streaming code

[ https://issues.apache.org/jira/browse/WSS-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-423: Summary: Support CRL checking for streaming code (was: Suuport CRL checking for streaming

[jira] [Created] (WSS-421) WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied to the security header

Colm O hEigeartaigh created WSS-421: --- Summary: WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied to the security header Key: WSS-421 URL:

[jira] [Resolved] (WSS-421) WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied to the security header

[ https://issues.apache.org/jira/browse/WSS-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-421. - Resolution: Fixed WSSecSignature does not allow access to the internal

[jira] [Created] (WSS-422) Move SAML Signature Profile Validation to the SamlAssertionValidator

Colm O hEigeartaigh created WSS-422: --- Summary: Move SAML Signature Profile Validation to the SamlAssertionValidator Key: WSS-422 URL: https://issues.apache.org/jira/browse/WSS-422 Project: WSS4J

[jira] [Resolved] (WSS-422) Move SAML Signature Profile Validation to the SamlAssertionValidator

[ https://issues.apache.org/jira/browse/WSS-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-422. - Resolution: Fixed Move SAML Signature Profile Validation to the SamlAssertionValidator

[jira] [Created] (WSS-420) Add the ability to explicitly allow/disallow UsernameTokens with no passwords

Colm O hEigeartaigh created WSS-420: --- Summary: Add the ability to explicitly allow/disallow UsernameTokens with no passwords Key: WSS-420 URL: https://issues.apache.org/jira/browse/WSS-420 Project:

[jira] [Commented] (WSS-419) failing after redeploy The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/WSS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552891#comment-13552891 ] Colm O hEigeartaigh commented on WSS-419: - I removed ThreadLocals from Santuario,

[jira] [Resolved] (WSS-419) failing after redeploy The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/WSS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-419. - Resolution: Won't Fix Fixed in Santuario. Colm. failing after redeploy

[jira] [Commented] (WSS-419) failing after redeploy The signature or decryption was invalid

[ https://issues.apache.org/jira/browse/WSS-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13549659#comment-13549659 ] Colm O hEigeartaigh commented on WSS-419: - I don't think this is an issue in either

[jira] [Created] (WSS-417) Cannot deploy WSS4J 1.6.8 to an OSGi container

Colm O hEigeartaigh created WSS-417: --- Summary: Cannot deploy WSS4J 1.6.8 to an OSGi container Key: WSS-417 URL: https://issues.apache.org/jira/browse/WSS-417 Project: WSS4J Issue Type: Bug

[jira] [Resolved] (WSS-417) Cannot deploy WSS4J 1.6.8 to an OSGi container

[ https://issues.apache.org/jira/browse/WSS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-417. - Resolution: Fixed Cannot deploy WSS4J 1.6.8 to an OSGi container

[jira] [Commented] (WSS-371) Add support for (custom) GCM algorithm-suites.

[ https://issues.apache.org/jira/browse/WSS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13531138#comment-13531138 ] Colm O hEigeartaigh commented on WSS-371: - Hi Marc, On second thoughts - let's

[jira] [Commented] (WSS-415) Reject RSA v1.5 Key Transport Algorithm by default

[ https://issues.apache.org/jira/browse/WSS-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530067#comment-13530067 ] Colm O hEigeartaigh commented on WSS-415: - Just WSS4J I think. Colm.

[jira] [Commented] (WSS-413) EncryptedKey security issue with streaming code

[ https://issues.apache.org/jira/browse/WSS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13530068#comment-13530068 ] Colm O hEigeartaigh commented on WSS-413: - No problem with handling this in

[jira] [Commented] (WSS-373) Check sender-vouches and holder-of-key requirements for SAML tokens.

[ https://issues.apache.org/jira/browse/WSS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527805#comment-13527805 ] Colm O hEigeartaigh commented on WSS-373: - Hi Marc, It's already taken care of (in

[jira] [Commented] (WSS-373) Check sender-vouches and holder-of-key requirements for SAML tokens.

[ https://issues.apache.org/jira/browse/WSS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13527951#comment-13527951 ] Colm O hEigeartaigh commented on WSS-373: - We could perhaps move some of the

[jira] [Commented] (WSS-416) Update ConditionsBean to support additional conditions such as Delegate

[ https://issues.apache.org/jira/browse/WSS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13511339#comment-13511339 ] Colm O hEigeartaigh commented on WSS-416: - Sure absolutely. Colm.

[jira] [Closed] (WSS-406) Add the ability to define which algorithms are acceptable when processing a security header

[ https://issues.apache.org/jira/browse/WSS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-406. --- Add the ability to define which algorithms are acceptable when processing a security header

[jira] [Closed] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-231. --- There is an issue with the position of the Timestamp element in the Security header when

[jira] [Closed] (WSS-399) WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though requested by W3C

[ https://issues.apache.org/jira/browse/WSS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-399. --- WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though requested by W3C

[jira] [Closed] (WSS-409) explicit dependency on XMLDSigRI in WSSConfig causes java.lang.ClassNotFoundException: org.apache.jcp.xml.dsig.internal.dom.XMLDSigRI on WAS 8.5

[ https://issues.apache.org/jira/browse/WSS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-409. --- explicit dependency on XMLDSigRI in WSSConfig causes java.lang.ClassNotFoundException:

[jira] [Closed] (WSS-410) Reduce dependency on xmlsec library

[ https://issues.apache.org/jira/browse/WSS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-410. --- Reduce dependency on xmlsec library ---

[jira] [Closed] (WSS-411) STRTransform does not work in certain circumstances

[ https://issues.apache.org/jira/browse/WSS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-411. --- STRTransform does not work in certain circumstances

[jira] [Closed] (WSS-407) Error when signing a SOAP Body that is encrypted with a reference to a SAML Token

[ https://issues.apache.org/jira/browse/WSS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-407. --- Error when signing a SOAP Body that is encrypted with a reference to a SAML Token

[jira] [Commented] (WSS-416) Update ConditionsBean to support additional conditions such as Delegate

[ https://issues.apache.org/jira/browse/WSS-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13509697#comment-13509697 ] Colm O hEigeartaigh commented on WSS-416: - Hi Yogesh, Would you consider submitting

[jira] [Created] (WSS-412) Unify error messages for the streaming code

Colm O hEigeartaigh created WSS-412: --- Summary: Unify error messages for the streaming code Key: WSS-412 URL: https://issues.apache.org/jira/browse/WSS-412 Project: WSS4J Issue Type:

[jira] [Created] (WSS-413) EncryptedKey security issue with streaming code

Colm O hEigeartaigh created WSS-413: --- Summary: EncryptedKey security issue with streaming code Key: WSS-413 URL: https://issues.apache.org/jira/browse/WSS-413 Project: WSS4J Issue Type:

[jira] [Created] (WSS-414) Ensure that Algorithms are checked in streaming code before they are used

Colm O hEigeartaigh created WSS-414: --- Summary: Ensure that Algorithms are checked in streaming code before they are used Key: WSS-414 URL: https://issues.apache.org/jira/browse/WSS-414 Project:

[jira] [Created] (WSS-415) Reject RSA v1.5 Key Transport Algorithm by default

Colm O hEigeartaigh created WSS-415: --- Summary: Reject RSA v1.5 Key Transport Algorithm by default Key: WSS-415 URL: https://issues.apache.org/jira/browse/WSS-415 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-406) Add the ability to define which algorithms are acceptable when processing a security header

[ https://issues.apache.org/jira/browse/WSS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-406. - Resolution: Fixed Add the ability to define which algorithms are acceptable when

[jira] [Resolved] (WSS-351) SAML work

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

[jira] [Resolved] (WSS-411) STRTransform does not work in certain circumstances

[ https://issues.apache.org/jira/browse/WSS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-411. - Resolution: Fixed STRTransform does not work in certain circumstances

[jira] [Commented] (WSS-354) Add support for specifying different algs for sign or c14n a SAML Assertion in the streaming code.

[ https://issues.apache.org/jira/browse/WSS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493859#comment-13493859 ] Colm O hEigeartaigh commented on WSS-354: - Hi Marc, Yep I think it makes sense to

[jira] [Commented] (WSS-356) Investigate signing Crypto differences

[ https://issues.apache.org/jira/browse/WSS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493861#comment-13493861 ] Colm O hEigeartaigh commented on WSS-356: - Hi Marc, Yes that's what I meant. I

[jira] [Commented] (WSS-355) Reconcile SAMLCallback between the two implementations

[ https://issues.apache.org/jira/browse/WSS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493866#comment-13493866 ] Colm O hEigeartaigh commented on WSS-355: - Hi Marc, The original issue was that the

[jira] [Commented] (WSS-354) Add support for specifying different algs for sign or c14n a SAML Assertion in the streaming code.

[ https://issues.apache.org/jira/browse/WSS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13493918#comment-13493918 ] Colm O hEigeartaigh commented on WSS-354: - Yep, assuming the SAMLCallback algorithms

[jira] [Commented] (WSS-400) Support processing an Embedded child of a SecurityTokenReference for the Stax code

[ https://issues.apache.org/jira/browse/WSS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486760#comment-13486760 ] Colm O hEigeartaigh commented on WSS-400: - Hi Marc, You're right, the DOM code

[jira] [Updated] (WSS-410) Reduce dependency on xmlsec library

[ https://issues.apache.org/jira/browse/WSS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-410: Fix Version/s: 1.6.8 Reduce dependency on xmlsec library

[jira] [Commented] (WSS-410) Reduce dependency on xmlsec library

[ https://issues.apache.org/jira/browse/WSS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486773#comment-13486773 ] Colm O hEigeartaigh commented on WSS-410: - Hi, I have applied a modified version of

[jira] [Commented] (WSS-410) Reduce dependency on xmlsec library

[ https://issues.apache.org/jira/browse/WSS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486863#comment-13486863 ] Colm O hEigeartaigh commented on WSS-410: - JSR-105 just covers XML Signature, and so

[jira] [Resolved] (WSS-410) Reduce dependency on xmlsec library

[ https://issues.apache.org/jira/browse/WSS-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-410. - Resolution: Fixed Reduce dependency on xmlsec library

[jira] [Updated] (WSS-409) explicit dependency on XMLDSigRI in WSSConfig causes java.lang.ClassNotFoundException: org.apache.jcp.xml.dsig.internal.dom.XMLDSigRI on WAS 8.5

[ https://issues.apache.org/jira/browse/WSS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-409: Fix Version/s: 1.6.8 explicit dependency on XMLDSigRI in WSSConfig causes

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476016#comment-13476016 ] Colm O hEigeartaigh commented on WSS-231: - If you want me to help you, you'll need

[jira] [Comment Edited] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476016#comment-13476016 ] Colm O hEigeartaigh edited comment on WSS-231 at 10/15/12 8:15 AM:

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471472#comment-13471472 ] Colm O hEigeartaigh commented on WSS-231: - Any update on this? I'll release 1.5.13

[jira] [Created] (WSS-407) Error when signing a SOAP Body that is encrypted with a reference to a SAML Token

Colm O hEigeartaigh created WSS-407: --- Summary: Error when signing a SOAP Body that is encrypted with a reference to a SAML Token Key: WSS-407 URL: https://issues.apache.org/jira/browse/WSS-407

[jira] [Resolved] (WSS-407) Error when signing a SOAP Body that is encrypted with a reference to a SAML Token

[ https://issues.apache.org/jira/browse/WSS-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-407. - Resolution: Fixed Error when signing a SOAP Body that is encrypted with a reference to

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466722#comment-13466722 ] Colm O hEigeartaigh commented on WSS-231: - Yes the change is committed. What web

[jira] [Created] (WSS-406) Add the ability to define which algorithms are acceptable when processing a security header

Colm O hEigeartaigh created WSS-406: --- Summary: Add the ability to define which algorithms are acceptable when processing a security header Key: WSS-406 URL: https://issues.apache.org/jira/browse/WSS-406

[jira] [Updated] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-401: Fix Version/s: (was: 1.5.13) Concurrency issue in generating signature under high

[jira] [Resolved] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-401. - Resolution: Incomplete Concurrency issue in generating signature under high load

[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13461729#comment-13461729 ] Colm O hEigeartaigh commented on WSS-401: - I am planning to call a vote on 1.5.13 at

[jira] [Assigned] (WSS-405) Support for XML Encryption 1.1 algorithms

[ https://issues.apache.org/jira/browse/WSS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-405: --- Assignee: Marc Giger (was: Colm O hEigeartaigh) Support for XML Encryption 1.1

[jira] [Resolved] (WSS-404) Store Subject from JAAS LoginContext in WSSecurityEngineResult

[ https://issues.apache.org/jira/browse/WSS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-404. - Resolution: Fixed Store Subject from JAAS LoginContext in WSSecurityEngineResult

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456888#comment-13456888 ] Colm O hEigeartaigh commented on WSS-231: - By the end of the month. Colm.

[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13456986#comment-13456986 ] Colm O hEigeartaigh commented on WSS-401: - Any update on this? Colm.

[jira] [Updated] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-231: Fix Version/s: 1.5.13 There is an issue with the position of the Timestamp element in

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449690#comment-13449690 ] Colm O hEigeartaigh commented on WSS-231: - It will be fixed for 1.5.13. Colm.

[jira] [Resolved] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-360. - Resolution: Fixed Port BSP enforcer to streaming code.

[jira] [Assigned] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-231: --- Assignee: Colm O hEigeartaigh (was: Ruchith Udayanga Fernando) There is an issue

[jira] [Updated] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-231: Fix Version/s: 1.6.8 There is an issue with the position of the Timestamp element in the

[jira] [Resolved] (WSS-311) Streaming-WebService-Security-Framework contribution/donation

[ https://issues.apache.org/jira/browse/WSS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-311. - Resolution: Fixed Streaming-WebService-Security-Framework contribution/donation

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448766#comment-13448766 ] Colm O hEigeartaigh commented on WSS-231: - It doesn't work prior to the fix I have

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448779#comment-13448779 ] Colm O hEigeartaigh commented on WSS-231: - You could switch to using WSS4J

[jira] [Comment Edited] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448779#comment-13448779 ] Colm O hEigeartaigh edited comment on WSS-231 at 9/6/12 1:33 AM:

[jira] [Commented] (WSS-231) There is an issue with the position of the Timestamp element in the Security header when using WSS4J calling .NET Web Services with WS-Security.

[ https://issues.apache.org/jira/browse/WSS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448795#comment-13448795 ] Colm O hEigeartaigh commented on WSS-231: - There are huge changes in 1.6.x compared

[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13447268#comment-13447268 ] Colm O hEigeartaigh commented on WSS-401: - Hi Hasini, Can you confirm if the bug

[jira] [Commented] (WSS-401) Concurrency issue in generating signature under high load

[ https://issues.apache.org/jira/browse/WSS-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443041#comment-13443041 ] Colm O hEigeartaigh commented on WSS-401: - Shouldn't the line

[jira] [Commented] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442408#comment-13442408 ] Colm O hEigeartaigh commented on WSS-360: - R3227 is now fixed. Colm.

[jira] [Comment Edited] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439649#comment-13439649 ] Colm O hEigeartaigh edited comment on WSS-360 at 8/28/12 12:34 AM:

[jira] [Comment Edited] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442408#comment-13442408 ] Colm O hEigeartaigh edited comment on WSS-360 at 8/28/12 12:35 AM:

[jira] [Closed] (WSS-334) SignatureProcessor does not fail when ids of referenced signed elements are duplicated

[ https://issues.apache.org/jira/browse/WSS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-334. --- SignatureProcessor does not fail when ids of referenced signed elements are duplicated

[jira] [Resolved] (WSS-334) SignatureProcessor does not fail when ids of referenced signed elements are duplicated

[ https://issues.apache.org/jira/browse/WSS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-334. - Resolution: Not A Problem SignatureProcessor does not fail when ids of referenced

[jira] [Comment Edited] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439649#comment-13439649 ] Colm O hEigeartaigh edited comment on WSS-360 at 8/23/12 10:08 PM:

[jira] [Created] (WSS-400) Support processing an Embedded child of a SecurityTokenReference for the Stax code

Colm O hEigeartaigh created WSS-400: --- Summary: Support processing an Embedded child of a SecurityTokenReference for the Stax code Key: WSS-400 URL: https://issues.apache.org/jira/browse/WSS-400

[jira] [Comment Edited] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439649#comment-13439649 ] Colm O hEigeartaigh edited comment on WSS-360 at 8/24/12 1:43 AM:

[jira] [Commented] (WSS-360) Port BSP enforcer to streaming code.

[ https://issues.apache.org/jira/browse/WSS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439649#comment-13439649 ] Colm O hEigeartaigh commented on WSS-360: - Hi Marc, I've moved the BSPRule stuff to

[jira] [Resolved] (WSS-365) Build issues

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

[jira] [Resolved] (WSS-361) Update code to use correct WSPasswordCallback code as per the DOM code.

[ https://issues.apache.org/jira/browse/WSS-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-361. - Resolution: Fixed Update code to use correct WSPasswordCallback code as per the DOM

[jira] [Resolved] (WSS-343) Move 1.6.x code into a new module.

[ https://issues.apache.org/jira/browse/WSS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-343. - Resolution: Fixed Move 1.6.x code into a new module.

[jira] [Resolved] (WSS-346) Refactor SAML functionality to be used by both implementations

[ https://issues.apache.org/jira/browse/WSS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-346. - Resolution: Fixed Refactor SAML functionality to be used by both implementations

[jira] [Commented] (WSS-353) Add support in the streaming code for decrypting an EncryptedKey in the Subject of a SAML Assertion.

[ https://issues.apache.org/jira/browse/WSS-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13437897#comment-13437897 ] Colm O hEigeartaigh commented on WSS-353: - See the commented out code here:

[jira] [Resolved] (WSS-367) Set up a parent pom with dependency management.

[ https://issues.apache.org/jira/browse/WSS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-367. - Resolution: Fixed Set up a parent pom with dependency management.

[jira] [Resolved] (WSS-344) Refactor Crypto functionality to be used by both implementations

[ https://issues.apache.org/jira/browse/WSS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-344. - Resolution: Fixed Refactor Crypto functionality to be used by both implementations

[jira] [Resolved] (WSS-345) Refactor Exception functionality to be used by both implementations

[ https://issues.apache.org/jira/browse/WSS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-345. - Resolution: Fixed Refactor Exception functionality to be used by both implementations

[jira] [Updated] (WSS-399) WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though requested by W3C

[ https://issues.apache.org/jira/browse/WSS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-399: Fix Version/s: 1.6.8 WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though

[jira] [Resolved] (WSS-399) WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though requested by W3C

[ https://issues.apache.org/jira/browse/WSS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-399. - Resolution: Fixed WSS4J: cannot set DigestMethod for KEYTRANSPORT_RSAOEP though

[jira] [Closed] (WSS-396) ConcurrentModificationException in MemoryReplayCache.processTokenExpiry

[ https://issues.apache.org/jira/browse/WSS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-396. --- ConcurrentModificationException in MemoryReplayCache.processTokenExpiry

[jira] [Closed] (WSS-393) WSS4J is not handling KeyIdentifier inside SecurityTokenReference inside a KeyInfo

[ https://issues.apache.org/jira/browse/WSS-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-393. --- WSS4J is not handling KeyIdentifier inside SecurityTokenReference inside a KeyInfo

<    5   6   7   8   9   10   11   12   13   14   >