[jira] [Commented] (WSS-475) Issue with multiple processing of ReferenceList in EncryptedKey element

[ https://issues.apache.org/jira/browse/WSS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756491#comment-13756491 ] Colm O hEigeartaigh commented on WSS-475: - Can this issue be resolved? Colm.

[jira] [Updated] (WSS-383) Allow encrypted password storage in signaturePropFile

[ https://issues.apache.org/jira/browse/WSS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-383: Fix Version/s: 2.0 Allow encrypted password storage in signaturePropFile

[jira] [Resolved] (WSS-383) Allow encrypted password storage in signaturePropFile

[ https://issues.apache.org/jira/browse/WSS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-383. - Resolution: Fixed Allow encrypted password storage in signaturePropFile

[jira] [Commented] (WSS-475) Issue with multiple processing of ReferenceList in EncryptedKey element

[ https://issues.apache.org/jira/browse/WSS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742325#comment-13742325 ] Colm O hEigeartaigh commented on WSS-475: - Hi Alessio, I have merged a potential fix

[jira] [Updated] (WSS-475) Issue with multiple processing of ReferenceList in EncryptedKey element

[ https://issues.apache.org/jira/browse/WSS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-475: Fix Version/s: 1.6.12 Issue with multiple processing of ReferenceList in EncryptedKey

[jira] [Created] (WSS-476) Add the ability to configure the Signature Canonicalization Algorithm via WSHandler

Colm O hEigeartaigh created WSS-476: --- Summary: Add the ability to configure the Signature Canonicalization Algorithm via WSHandler Key: WSS-476 URL: https://issues.apache.org/jira/browse/WSS-476

[jira] [Resolved] (WSS-472) Incorrect Symmetric Key Derivation Length validation

[ https://issues.apache.org/jira/browse/WSS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-472. - Resolution: Fixed Incorrect Symmetric Key Derivation Length validation

[jira] [Resolved] (WSS-438) Support Signature Cert Constraints as per the DOM code

[ https://issues.apache.org/jira/browse/WSS-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-438. - Resolution: Fixed Support Signature Cert Constraints as per the DOM code

[jira] [Resolved] (WSS-470) AsymmetricBinding + ProtectTokens validation not working

[ https://issues.apache.org/jira/browse/WSS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-470. - Resolution: Fixed AsymmetricBinding + ProtectTokens validation not working

[jira] [Resolved] (WSS-471) AsymmetricBinding validation without IncludeTimestamp doesn't work

[ https://issues.apache.org/jira/browse/WSS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-471. - Resolution: Not A Problem Not a problem after all, the test-policy was missing a

[jira] [Resolved] (WSS-473) BST signature element

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

[jira] [Updated] (WSS-464) Support the EncryptBeforeSigning + EncryptSignature policies

[ https://issues.apache.org/jira/browse/WSS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-464: Fix Version/s: 2.0 Support the EncryptBeforeSigning + EncryptSignature policies

[jira] [Updated] (WSS-418) Cannot configure SAML properties in WSS4JOutInterceptor without having to add that config file in the classpath

[ https://issues.apache.org/jira/browse/WSS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-418: Fix Version/s: 1.6.12 Cannot configure SAML properties in WSS4JOutInterceptor without

[jira] [Resolved] (WSS-418) Cannot configure SAML properties in WSS4JOutInterceptor without having to add that config file in the classpath

[ https://issues.apache.org/jira/browse/WSS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-418. - Resolution: Fixed Cannot configure SAML properties in WSS4JOutInterceptor without

[jira] [Created] (WSS-472) Incorrect Symmetric Key Derivation Length validation

Colm O hEigeartaigh created WSS-472: --- Summary: Incorrect Symmetric Key Derivation Length validation Key: WSS-472 URL: https://issues.apache.org/jira/browse/WSS-472 Project: WSS4J Issue

[jira] [Resolved] (WSS-460) Support RequireSignatureConfirmation policy validation

[ https://issues.apache.org/jira/browse/WSS-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-460. - Resolution: Fixed Support RequireSignatureConfirmation policy validation

[jira] [Created] (WSS-471) AsymmetricBinding validation without IncludeTimestamp doesn't work

Colm O hEigeartaigh created WSS-471: --- Summary: AsymmetricBinding validation without IncludeTimestamp doesn't work Key: WSS-471 URL: https://issues.apache.org/jira/browse/WSS-471 Project: WSS4J

[jira] [Created] (WSS-469) Symmetric Binding + Derived Keys is not currently working

Colm O hEigeartaigh created WSS-469: --- Summary: Symmetric Binding + Derived Keys is not currently working Key: WSS-469 URL: https://issues.apache.org/jira/browse/WSS-469 Project: WSS4J

[jira] [Created] (WSS-468) Symmetric Binding + EncryptBeforeSigning puts the Signature in front of the EncryptedKey

Colm O hEigeartaigh created WSS-468: --- Summary: Symmetric Binding + EncryptBeforeSigning puts the Signature in front of the EncryptedKey Key: WSS-468 URL: https://issues.apache.org/jira/browse/WSS-468

[jira] [Resolved] (WSS-467) Support creating SAML 2.0 Tokens with the AuthnStatement SessionNotOnOrAfter attribute.

[ https://issues.apache.org/jira/browse/WSS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-467. - Resolution: Fixed Support creating SAML 2.0 Tokens with the AuthnStatement

[jira] [Updated] (WSS-465) Possible information leak: incremental IDs

[ https://issues.apache.org/jira/browse/WSS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-465: Fix Version/s: 1.6.12 Possible information leak: incremental IDs

[jira] [Resolved] (WSS-465) Possible information leak: incremental IDs

[ https://issues.apache.org/jira/browse/WSS-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-465. - Resolution: Fixed Possible information leak: incremental IDs

[jira] [Resolved] (WSS-462) ProtectionOrderAssertionState.testProtectionOrder is not working

[ https://issues.apache.org/jira/browse/WSS-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-462. - Resolution: Fixed ProtectionOrderAssertionState.testProtectionOrder is not working

[jira] [Resolved] (WSS-446) Enable SignatureConfirmation without a Signature

[ https://issues.apache.org/jira/browse/WSS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-446. - Resolution: Fixed Enable SignatureConfirmation without a Signature

[jira] [Commented] (WSS-459) RequiredParts + EncryptedParts policy validation not working

[ https://issues.apache.org/jira/browse/WSS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706825#comment-13706825 ] Colm O hEigeartaigh commented on WSS-459: - Is a fix required in CXF for this issue

[jira] [Created] (WSS-462) ProtectionOrderAssertionState.testProtectionOrder is not working

Colm O hEigeartaigh created WSS-462: --- Summary: ProtectionOrderAssertionState.testProtectionOrder is not working Key: WSS-462 URL: https://issues.apache.org/jira/browse/WSS-462 Project: WSS4J

[jira] [Commented] (WSS-461) org.apache.ws.security.processor.SignatureProcessor does not allow to add custom resolver

[ https://issues.apache.org/jira/browse/WSS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13706844#comment-13706844 ] Colm O hEigeartaigh commented on WSS-461: - You can access the source code here:

[jira] [Created] (WSS-463) Refactor Signature + Encryption referencing

Colm O hEigeartaigh created WSS-463: --- Summary: Refactor Signature + Encryption referencing Key: WSS-463 URL: https://issues.apache.org/jira/browse/WSS-463 Project: WSS4J Issue Type: Bug

[jira] [Commented] (WSS-459) RequiredParts + EncryptedParts policy validation not working

[ https://issues.apache.org/jira/browse/WSS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707044#comment-13707044 ] Colm O hEigeartaigh commented on WSS-459: - Hi Marc, In that case why aren't

[jira] [Resolved] (WSS-457) Incorrect validation of ProtectTokens assertion

[ https://issues.apache.org/jira/browse/WSS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-457. - Resolution: Fixed Incorrect validation of ProtectTokens assertion

[jira] [Created] (WSS-460) Support RequireSignatureConfirmation policy validation

Colm O hEigeartaigh created WSS-460: --- Summary: Support RequireSignatureConfirmation policy validation Key: WSS-460 URL: https://issues.apache.org/jira/browse/WSS-460 Project: WSS4J Issue

[jira] [Created] (WSS-459) RequiredParts policy validation not working

Colm O hEigeartaigh created WSS-459: --- Summary: RequiredParts policy validation not working Key: WSS-459 URL: https://issues.apache.org/jira/browse/WSS-459 Project: WSS4J Issue Type: Bug

[jira] [Updated] (WSS-446) Enable SignatureConfirmation without a Signature

[ https://issues.apache.org/jira/browse/WSS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-446: Description: There does not appear to be a way to enable SignatureConfirmation in WSS4J 2.0

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

Colm O hEigeartaigh created WSS-456: --- Summary: Not possible to support SymmetricBinding ProtectTokens policy Key: WSS-456 URL: https://issues.apache.org/jira/browse/WSS-456 Project: WSS4J

[jira] [Commented] (WSS-457) Incorrect validation of ProtectTokens assertion

[ https://issues.apache.org/jira/browse/WSS-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694027#comment-13694027 ] Colm O hEigeartaigh commented on WSS-457: - See the test in StaxX509TokenTest in CXF.

[jira] [Created] (WSS-457) Incorrect validation of ProtectTokens assertion

Colm O hEigeartaigh created WSS-457: --- Summary: Incorrect validation of ProtectTokens assertion Key: WSS-457 URL: https://issues.apache.org/jira/browse/WSS-457 Project: WSS4J Issue Type:

[jira] [Resolved] (WSS-455) Certificate validation in SignatureTrustValidator

[ https://issues.apache.org/jira/browse/WSS-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-455. - Resolution: Fixed Certificate validation in SignatureTrustValidator

[jira] [Resolved] (WSS-454) TokenProtection error

[ https://issues.apache.org/jira/browse/WSS-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-454. - Resolution: Fixed Fix confirmed, thanks. Colm. TokenProtection error

[jira] [Resolved] (WSS-453) Once Token Inclusion handling is not working

[ https://issues.apache.org/jira/browse/WSS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-453. - Resolution: Fixed Fix confirmed, thanks. Colm. Once Token Inclusion

[jira] [Resolved] (WSS-448) OnlySignEntireHeadersAndBody policy validation is incorrect

[ https://issues.apache.org/jira/browse/WSS-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-448. - Resolution: Fixed OnlySignEntireHeadersAndBody policy validation is incorrect

[jira] [Resolved] (WSS-443) Treat tokens received over TLS as encrypted

[ https://issues.apache.org/jira/browse/WSS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-443. - Resolution: Fixed Fix confirmed, thanks. Colm. Treat tokens received

[jira] [Resolved] (WSS-450) Inbound Processing code fails with an Encrypted Signature

[ https://issues.apache.org/jira/browse/WSS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-450. - Resolution: Fixed Assignee: Marc Giger Fix confirmed, thanks. Colm.

[jira] [Created] (WSS-453) Once Token Inclusion handling is not working

Colm O hEigeartaigh created WSS-453: --- Summary: Once Token Inclusion handling is not working Key: WSS-453 URL: https://issues.apache.org/jira/browse/WSS-453 Project: WSS4J Issue Type: Bug

[jira] [Assigned] (WSS-453) Once Token Inclusion handling is not working

[ https://issues.apache.org/jira/browse/WSS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-453: --- Assignee: Marc Giger (was: Colm O hEigeartaigh) Once Token Inclusion handling is

[jira] [Assigned] (WSS-449) Receiving code can't handle the case of a Thumbprint reference to a BST in the token

[ https://issues.apache.org/jira/browse/WSS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-449: --- Assignee: Marc Giger Receiving code can't handle the case of a Thumbprint

[jira] [Assigned] (WSS-442) Never Token Inclustion is not handled correctly (for X.509 tokens)

[ https://issues.apache.org/jira/browse/WSS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-442: --- Assignee: Marc Giger (was: Colm O hEigeartaigh) Never Token Inclustion is not

[jira] [Resolved] (WSS-449) Receiving code can't handle the case of a Thumbprint reference to a BST in the token

[ https://issues.apache.org/jira/browse/WSS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-449. - Resolution: Fixed Fix confirmed, thanks! Colm. Receiving code can't

[jira] [Resolved] (WSS-442) Never Token Inclustion is not handled correctly (for X.509 tokens)

[ https://issues.apache.org/jira/browse/WSS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-442. - Resolution: Fixed Fix confirmed, thanks. Colm. Never Token Inclustion

[jira] [Created] (WSS-454) TokenProtection error

Colm O hEigeartaigh created WSS-454: --- Summary: TokenProtection error Key: WSS-454 URL: https://issues.apache.org/jira/browse/WSS-454 Project: WSS4J Issue Type: Bug Reporter:

[jira] [Resolved] (WSS-441) Allow the date/time in the security headers to be spoofed

[ https://issues.apache.org/jira/browse/WSS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-441. - Resolution: Fixed Allow the date/time in the security headers to be spoofed

[jira] [Commented] (WSS-441) Allow the date/time in the security headers to be spoofed

[ https://issues.apache.org/jira/browse/WSS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13678113#comment-13678113 ] Colm O hEigeartaigh commented on WSS-441: - I've committed a modified version of this

[jira] [Commented] (WSS-451) Fixed namespace prefix when creating elements in SecurityTokenReference.java

[ https://issues.apache.org/jira/browse/WSS-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670336#comment-13670336 ] Colm O hEigeartaigh commented on WSS-451: - Where is the SecurityTokenReference being

[jira] [Created] (WSS-450) Inbound Processing code fails with an Encrypted Signature

Colm O hEigeartaigh created WSS-450: --- Summary: Inbound Processing code fails with an Encrypted Signature Key: WSS-450 URL: https://issues.apache.org/jira/browse/WSS-450 Project: WSS4J

[jira] [Commented] (WSS-448) OnlySignEntireHeadersAndBody policy validation is incorrect

[ https://issues.apache.org/jira/browse/WSS-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669244#comment-13669244 ] Colm O hEigeartaigh commented on WSS-448: - Yep that's it. Colm.

[jira] [Commented] (WSS-450) Inbound Processing code fails with an Encrypted Signature

[ https://issues.apache.org/jira/browse/WSS-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669247#comment-13669247 ] Colm O hEigeartaigh commented on WSS-450: - Ok thanks. Looks like there is a bug in

[jira] [Created] (WSS-447) Add the ability to include the signing token for IssuerSerial/Thumbprint Reference cases

Colm O hEigeartaigh created WSS-447: --- Summary: Add the ability to include the signing token for IssuerSerial/Thumbprint Reference cases Key: WSS-447 URL: https://issues.apache.org/jira/browse/WSS-447

[jira] [Resolved] (WSS-447) Add the ability to include the signing token for IssuerSerial/Thumbprint Reference cases

[ https://issues.apache.org/jira/browse/WSS-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-447. - Resolution: Fixed Add the ability to include the signing token for

[jira] [Created] (WSS-448) OnlySignEntireHeadersAndBody policy validation is incorrect

Colm O hEigeartaigh created WSS-448: --- Summary: OnlySignEntireHeadersAndBody policy validation is incorrect Key: WSS-448 URL: https://issues.apache.org/jira/browse/WSS-448 Project: WSS4J

[jira] [Created] (WSS-449) Receiving code can't handle the case of a Thumbprint reference to a BST in the token

Colm O hEigeartaigh created WSS-449: --- Summary: Receiving code can't handle the case of a Thumbprint reference to a BST in the token Key: WSS-449 URL: https://issues.apache.org/jira/browse/WSS-449

[jira] [Created] (WSS-446) Enable SignatureConfirmation without a Signature

Colm O hEigeartaigh created WSS-446: --- Summary: Enable SignatureConfirmation without a Signature Key: WSS-446 URL: https://issues.apache.org/jira/browse/WSS-446 Project: WSS4J Issue Type:

[jira] [Commented] (WSS-443) Treat tokens received over TLS as encrypted

[ https://issues.apache.org/jira/browse/WSS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662832#comment-13662832 ] Colm O hEigeartaigh commented on WSS-443: - It works for the UsernameToken case I

[jira] [Assigned] (WSS-443) Treat tokens received over TLS as encrypted

[ https://issues.apache.org/jira/browse/WSS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-443: --- Assignee: Marc Giger Treat tokens received over TLS as encrypted

[jira] [Commented] (WSS-443) Treat tokens received over TLS as encrypted

[ https://issues.apache.org/jira/browse/WSS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662891#comment-13662891 ] Colm O hEigeartaigh commented on WSS-443: - Hi Marc, The spec also says (8.3): If

[jira] [Created] (WSS-444) Add support for WS-SecurityPolicy Strict validation

Colm O hEigeartaigh created WSS-444: --- Summary: Add support for WS-SecurityPolicy Strict validation Key: WSS-444 URL: https://issues.apache.org/jira/browse/WSS-444 Project: WSS4J Issue

[jira] [Created] (WSS-443) Treat tokens received over TLS as encrypted

Colm O hEigeartaigh created WSS-443: --- Summary: Treat tokens received over TLS as encrypted Key: WSS-443 URL: https://issues.apache.org/jira/browse/WSS-443 Project: WSS4J Issue Type: Bug

[jira] [Updated] (WSS-443) Treat tokens received over TLS as encrypted

[ https://issues.apache.org/jira/browse/WSS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-443: Description: The streaming WS-Security code treats a UsernameToken received over TLS as a

[jira] [Commented] (WSS-440) BSPEnforcer doesn't accept valid references of type X509PKIPathv1

[ https://issues.apache.org/jira/browse/WSS-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647475#comment-13647475 ] Colm O hEigeartaigh commented on WSS-440: - Hi Anli, Your patch is incorrect, as is

[jira] [Commented] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642703#comment-13642703 ] Colm O hEigeartaigh commented on WSS-436: - Hi Marc, Thanks, fix confirmed. However,

[jira] [Commented] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642718#comment-13642718 ] Colm O hEigeartaigh commented on WSS-436: - Hi Marc, Yes it does work in the DOM

[jira] [Assigned] (WSS-437) Error in using StaX WS-Security + CXF WS-Addressing

[ https://issues.apache.org/jira/browse/WSS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-437: --- Assignee: Marc Giger Can be resolved. Colm. Error in using StaX

[jira] [Created] (WSS-438) Support Signature Cert Constraints as per the DOM code

Colm O hEigeartaigh created WSS-438: --- Summary: Support Signature Cert Constraints as per the DOM code Key: WSS-438 URL: https://issues.apache.org/jira/browse/WSS-438 Project: WSS4J Issue

[jira] [Commented] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13642753#comment-13642753 ] Colm O hEigeartaigh commented on WSS-436: - What about for LaxTsFirst policies? If we

[jira] [Commented] (WSS-437) Error in using StaX WS-Security + CXF WS-Addressing

[ https://issues.apache.org/jira/browse/WSS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640277#comment-13640277 ] Colm O hEigeartaigh commented on WSS-437: - Cool, thanks Marc! Colm.

[jira] [Reopened] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reopened WSS-436: - Outbound StaX code should fail on not finding a signature/encryption part

[jira] [Commented] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640450#comment-13640450 ] Colm O hEigeartaigh commented on WSS-436: - Hi Marc, This issue is not entirely

[jira] [Commented] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

[ https://issues.apache.org/jira/browse/WSS-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13639023#comment-13639023 ] Colm O hEigeartaigh commented on WSS-436: - I guess it should be done in Santuario

[jira] [Created] (WSS-437) Error in using StaX WS-Security + CXF WS-Addressing

Colm O hEigeartaigh created WSS-437: --- Summary: Error in using StaX WS-Security + CXF WS-Addressing Key: WSS-437 URL: https://issues.apache.org/jira/browse/WSS-437 Project: WSS4J Issue

[jira] [Created] (WSS-436) Outbound StaX code should fail on not finding a signature/encryption part

Colm O hEigeartaigh created WSS-436: --- Summary: Outbound StaX code should fail on not finding a signature/encryption part Key: WSS-436 URL: https://issues.apache.org/jira/browse/WSS-436 Project:

[jira] [Resolved] (WSS-434) Add ValueType attribute to a Signature/Encryption Reference to a DerivedKeyToken

[ https://issues.apache.org/jira/browse/WSS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-434. - Resolution: Fixed Add ValueType attribute to a Signature/Encryption Reference to a

[jira] [Created] (WSS-434) Add ValueType attribute to a Signature/Encryption Reference to a DerivedKeyToken

Colm O hEigeartaigh created WSS-434: --- Summary: Add ValueType attribute to a Signature/Encryption Reference to a DerivedKeyToken Key: WSS-434 URL: https://issues.apache.org/jira/browse/WSS-434

[jira] [Created] (WSS-433) Specifying actions of WSSConstants.SIGNATURE_CONFIRMATION, WSSConstants.SIGNATURE hangs WSS4J

Colm O hEigeartaigh created WSS-433: --- Summary: Specifying actions of WSSConstants.SIGNATURE_CONFIRMATION, WSSConstants.SIGNATURE hangs WSS4J Key: WSS-433 URL: https://issues.apache.org/jira/browse/WSS-433

[jira] [Commented] (WSS-433) Specifying actions of WSSConstants.SIGNATURE_CONFIRMATION, WSSConstants.SIGNATURE hangs WSS4J

[ https://issues.apache.org/jira/browse/WSS-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630221#comment-13630221 ] Colm O hEigeartaigh commented on WSS-433: - Hi Marc, In addition to this bug, I

[jira] [Updated] (WSS-432) Support EncryptedKeySHA1 KeyIdentifier in the StaX code

[ https://issues.apache.org/jira/browse/WSS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-432: Fix Version/s: 2.0 Support EncryptedKeySHA1 KeyIdentifier in the StaX code

[jira] [Resolved] (WSS-359) Streaming WS-Security support

[ https://issues.apache.org/jira/browse/WSS-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-359. - Resolution: Fixed Streaming WS-Security support -

[jira] [Resolved] (WSS-348) Refactor Caching nonces/timestamp functionality to be used by both implementations

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

[jira] [Resolved] (WSS-342) Refactoring

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

[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=13619730#comment-13619730 ] Colm O hEigeartaigh commented on WSS-363: - Looks good thanks! Colm.

[jira] [Closed] (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 closed WSS-422. --- Move SAML Signature Profile Validation to the SamlAssertionValidator

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

[ https://issues.apache.org/jira/browse/WSS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-424. --- Signature Element is not inserted in the correct place in the header in certain

[jira] [Closed] (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 closed WSS-420. --- Add the ability to explicitly allow/disallow UsernameTokens with no passwords

[jira] [Closed] (WSS-431) Performance bottleneck in MemoryReplayCache on high load

[ https://issues.apache.org/jira/browse/WSS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-431. --- Performance bottleneck in MemoryReplayCache on high load

[jira] [Closed] (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 closed WSS-427. --- Add support for processing UsernameToken Created Dates

[jira] [Closed] (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 closed WSS-421. --- WSSecSignature does not allow access to the internal BinarySecurityToken after it is applied

[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=13612754#comment-13612754 ] Colm O hEigeartaigh commented on WSS-363: - Hi Marc, I pushed a fix to share

[jira] [Updated] (WSS-428) It should be possible to use the useReqSigCert even when the certificate is not sent in the request

[ https://issues.apache.org/jira/browse/WSS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-428: Fix Version/s: (was: 1.6.10) It should be possible to use the useReqSigCert even

[jira] [Commented] (WSS-428) It should be possible to use the useReqSigCert even when the certificate is not sent in the request

[ https://issues.apache.org/jira/browse/WSS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13606498#comment-13606498 ] Colm O hEigeartaigh commented on WSS-428: - Is this still an issue? I'm going to move

[jira] [Updated] (WSS-431) Performance bottleneck in MemoryReplayCache on high load

[ https://issues.apache.org/jira/browse/WSS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-431: Fix Version/s: 1.6.10 Performance bottleneck in MemoryReplayCache on high load

[jira] [Resolved] (WSS-431) Performance bottleneck in MemoryReplayCache on high load

[ https://issues.apache.org/jira/browse/WSS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-431. - Resolution: Fixed Performance bottleneck in MemoryReplayCache on high load

[jira] [Created] (WSS-429) Consider some @Deprecated classes in the old namespace

Colm O hEigeartaigh created WSS-429: --- Summary: Consider some @Deprecated classes in the old namespace Key: WSS-429 URL: https://issues.apache.org/jira/browse/WSS-429 Project: WSS4J Issue

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

Colm O hEigeartaigh created WSS-427: --- Summary: Add support for processing UsernameToken Created Dates Key: WSS-427 URL: https://issues.apache.org/jira/browse/WSS-427 Project: WSS4J Issue

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