wss4j-dev  

Messages by Thread

• svn commit: r948399 - in /webservices/wss4j/trunk: src/org/apache/ws/security/components/crypto/CryptoBase.java src/org/apache/ws/security/message/EnvelopeIdResolver.java test/wssec/TestWSSecurityWSS86.java coheigea
• svn commit: r948393 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/components/crypto/CryptoBase.java test/wssec/TestWSSecurityWSS86.java coheigea
• svn commit: r948389 - /webservices/wss4j/trunk/test/wssec/TestWSSecurityNew3.java coheigea
• svn commit: r948388 - /webservices/wss4j/branches/1_5_x-fixes/test/wssec/TestWSSecurityNew3.java coheigea
• svn commit: r947604 - in /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security: WSDocInfo.java message/EnvelopeIdResolver.java message/WSSecSignature.java saml/WSSecSignatureSAML.java coheigea
• [jira] Created: (WSS-232) Performance Improvement in WSSConfig Mario Siegenthaler (JIRA)
  • [jira] Updated: (WSS-232) Performance Improvement in WSSConfig Mario Siegenthaler (JIRA)
• svn commit: r945177 - in /webservices/wss4j/trunk: src/org/apache/ws/security/processor/ src/org/apache/ws/security/transform/ test/ test/wssec/ coheigea
• svn commit: r945175 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/processor/ src/org/apache/ws/security/transform/ test/ test/wssec/ coheigea
• [jira] Created: (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. Chris Weitner (JIRA)
  • Re: [jira] Created: (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. Werner Dittmann
  • [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. Colm O hEigeartaigh (JIRA)
  • [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. Chris Weitner (JIRA)
  • [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. Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-230) WSS4JInInterceptor.getAction throws "No security action was defined" when using Spring default-autowire="byType" Cheng Lee (JIRA)
  • [jira] Updated: (WSS-230) WSS4JInInterceptor.getAction throws "No security action was defined" when using Spring default-autowire="byType" Cheng Lee (JIRA)
  • [jira] Commented: (WSS-230) WSS4JInInterceptor.getAction throws "No security action was defined" when using Spring default-autowire="byType" Daniel Kulp (JIRA)
  • [jira] Commented: (WSS-230) WSS4JInInterceptor.getAction throws "No security action was defined" when using Spring default-autowire="byType" Cheng Lee (JIRA)
  • [jira] Commented: (WSS-230) WSS4JInInterceptor.getAction throws "No security action was defined" when using Spring default-autowire="byType" Cheng Lee (JIRA)
• RE: WSS-146 Martin Gainty
• Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Ruchith Fernando
  • Re: Performance Comparison Daniel Kulp
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Daniel Kulp
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Dennis Sosnoski
  • Re: Performance Comparison Andreas Veithen
  • Re: Performance Comparison Daniel Kulp
  • Re: Performance Comparison Andreas Veithen
• wss4j performance results..... Daniel Kulp
  • RE: wss4j performance results..... Colm O hEigeartaigh
  • Re: wss4j performance results..... Daniel Kulp
  • Re: wss4j performance results..... Dennis Sosnoski
• [jira] Created: (WSS-229) UsernameTokenProcessor should be able to act as a UsernameToken parser only and not enforce the validation of passwords Sergey Beryozkin (JIRA)
  • [jira] Updated: (WSS-229) UsernameTokenProcessor should be able to act as a UsernameToken parser only and not enforce the validation of passwords Sergey Beryozkin (JIRA)
  • [jira] Resolved: (WSS-229) UsernameTokenProcessor should be able to act as a UsernameToken parser only and not enforce the validation of passwords Sergey Beryozkin (JIRA)
• Certificate X509v3 vs X509v1 Andrea Poli
  • RE: Certificate X509v3 vs X509v1 Colm O hEigeartaigh
• svn commit: r934737 - /webservices/wss4j/trunk/src/org/apache/ws/security/components/crypto/CryptoBase.java coheigea
• svn commit: r934734 - /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security/components/crypto/CryptoBase.java coheigea
• svn commit: r934414 - in /webservices/wss4j/branches/1_5_x-fixes: keys/ test/ test/wssec/ coheigea
• [IMPORTANT] Web Services Board Report, and discussion Glen Daniels
• WSS-222 Status David Valeri
• [jira] Created: (WSS-228) Encryption with a UsernameToken is (almost) broken Evan Leonard (JIRA)
  • [jira] Commented: (WSS-228) Encryption with a UsernameToken is (almost) broken Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-227) CryptoBase.getPrivateKey() unable to handle empty (null) passwords Paul Rogalinski (JIRA)
  • [jira] Assigned: (WSS-227) CryptoBase.getPrivateKey() unable to handle empty (null) passwords Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-227) CryptoBase.getPrivateKey() unable to handle empty (null) passwords Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-227) CryptoBase.getPrivateKey() unable to handle empty (null) passwords Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-227) CryptoBase.getPrivateKey() unable to handle empty (null) passwords Colm O hEigeartaigh (JIRA)
• when is 1.5.9 to be released? hwachung feng
• [jira] Created: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Pankaj gupta (JIRA)
  • [jira] Commented: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Gupta, Pankaj FBSI (JIRA)
  • [jira] Commented: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-226) Interoperability b/w Java consumer of .NET Web Service with WS-Security on WSE 2.0 Colm O hEigeartaigh (JIRA)
• WSS4J support for OpenSAML 2 library Avijit Ajay
  • RE: WSS4J support for OpenSAML 2 library Martin Gainty
  • Re: WSS4J support for OpenSAML 2 library George Stanchev
  • Re: WSS4J support for OpenSAML 2 library Daniel Kulp
  • Re: WSS4J support for OpenSAML 2 library Thilina Mahesh Buddhika
  • Re: WSS4J support for OpenSAML 2 library Daniel Kulp
  • Re: WSS4J support for OpenSAML 2 library Sanjiva Weerawarana
• [jira] Created: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Tom Trader (JIRA)
  • [jira] Assigned: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Tom Trader (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Tom Trader (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Tom Trader (JIRA)
  • [jira] Closed: (WSS-225) 'Unprintable' characters in Distinguished Name causing comparison failure Colm O hEigeartaigh (JIRA)
• WS-Security Encryption/Decryption Advice Sebastian Krueger
  • Re: WS-Security Encryption/Decryption Advice Dennis Sosnoski
  • Re: WS-Security Encryption/Decryption Advice Sebastian Krueger
• Problem with null or empty Namespace in encryption parts Matthias Richter
  • Re: Problem with null or empty Namespace in encryption parts chrajanirao
• How do I read WSS Username Token after validation? Lucaluke
  • Re: How do I read WSS Username Token after validation? Daniel Kulp
  • Re: How do I read WSS Username Token after validation? Lucaluke
  • Re: How do I read WSS Username Token after validation? Thilina Mahesh Buddhika
• Optional encryption/decryption Siarhei Kaneuski
  • Re: Optional encryption/decryption Werner Dittmann
  • Re: Optional encryption/decryption Siarhei Kaneuski
  • Re: Optional encryption/decryption Daniel Kulp
  • RE: Optional encryption/decryption Hannes Angst
  • Re: Optional encryption/decryption Daniel Kulp
  • RE: Optional encryption/decryption Siarhei Kaneuski
• svn commit: r901148 - in /webservices/wss4j/trunk: src/org/apache/ws/security/action/SAMLTokenSignedAction.java test/wssec/TestWSSecurityNewST3.java coheigea
• svn commit: r901147 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/action/SAMLTokenSignedAction.java src/org/apache/ws/security/saml/WSSecSignatureSAML.java test/wssec/TestWSSecurityNewST3.java coheigea
• svn commit: r900368 - in /webservices/wss4j/trunk: src/org/apache/ws/security/processor/ReferenceListProcessor.java test/wssec/TestWSSecurityEncryptionParts.java coheigea
• svn commit: r900367 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/processor/ReferenceListProcessor.java test/wssec/TestWSSecurityEncryptionParts.java coheigea
• svn commit: r900355 - /webservices/wss4j/trunk/src/org/apache/ws/security/util/UUIDGenerator.java coheigea
• svn commit: r900353 - /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security/util/UUIDGenerator.java coheigea
• Re: Java updates for Mac OS changes the password on jre_home/lib/security/cacerts Andreas Veithen
  • RE: Java updates for Mac OS changes the password on jre_home/lib/security/cacerts Colm O hEigeartaigh
• [jira] Created: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration David Valeri (JIRA)
  • [jira] Updated: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration David Valeri (JIRA)
  • [jira] Updated: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration Colm O hEigeartaigh (JIRA)
  • [jira] Assigned: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-224) SAMLTokenSignedAction and WSSecSignatureSAML do not honor signature algorithm or digest algorithm from WSSHandler configuration Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance. todd wolff (JIRA)
  • [jira] Updated: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance. todd wolff (JIRA)
  • [jira] Updated: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance. Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance. Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-223) Incorrect xpath set on WSDataRef when decrypting an EncryptedHeader instance. Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform David Valeri (JIRA)
  • [jira] Updated: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform David Valeri (JIRA)
  • [jira] Assigned: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-222) SignatureProcessor does not provide correct signature coverage results with STR Dereference Transform Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Dave Bryant (JIRA)
  • [jira] Commented: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Daniel Kulp (JIRA)
  • [jira] Commented: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Dave Bryant (JIRA)
  • [jira] Updated: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-221) UUIDGenerator generates duplicate identifiers when used in a multi-threaded environment Colm O hEigeartaigh (JIRA)
• Board reports for January (WS and Axis) Glen Daniels
• svn commit: r895991 - /webservices/wss4j/trunk/src/org/apache/ws/security/handler/WSHandler.java coheigea
• svn commit: r895988 - /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security/handler/WSHandler.java coheigea
• [jira] Created: (WSS-220) WSHandler is using default configuration Tomasz Pik (JIRA)
  • [jira] Updated: (WSS-220) WSHandler is using default configuration Tomasz Pik (JIRA)
  • [jira] Assigned: (WSS-220) WSHandler is using default configuration Colm O hEigeartaigh (JIRA)
  • [jira] Updated: (WSS-220) WSHandler is using default configuration Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-220) WSHandler is using default configuration Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-220) WSHandler is using default configuration Colm O hEigeartaigh (JIRA)
• [jira] Created: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string kumar ashutosh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string kumar ashutosh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string JIRA
  • [jira] Reopened: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string kumar ashutosh (JIRA)
  • [jira] Assigned: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string JIRA
  • [jira] Updated: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-219) empty/blank password not supported in username token. value read by wss4j is null instead of empty string Colm O hEigeartaigh (JIRA)
• a sample wss4j project for a self signed cert? Mike Borozdin
• Issue while using multiple webservices with WSS4J Amol Amol
• Fwd: Question about x509 certificates Cole Ferrier
  • RE: Question about x509 certificates Dittmann, Werner (NSN - DE/Munich)
  • Antwort: RE: Question about x509 certificates Oliver Wulff
• how to have usernmae token authentication and SecureConversation using rampart soni swapna
• Axis 1.1 with WSS4J Pradhan, Priyatosh (MLX Technology)
• keyStore.isKeyEntry() returning false NewToGit
  • RE: keyStore.isKeyEntry() returning false Dittmann, Werner (NSN - DE/Munich)
• Wss4j working with WebSphere? Yang, Gang CTR USA
  • RE: Wss4j working with WebSphere? Yang, Gang CTR USA
  • RE: Wss4j working with WebSphere? Colm O hEigeartaigh
  • RE: Wss4j working with WebSphere? Yang, Gang CTR USA
  • RE: Wss4j working with WebSphere? Colm O hEigeartaigh
  • RE: Wss4j working with WebSphere? Yang, Gang CTR USA
  • RE: Wss4j working with WebSphere? Colm O hEigeartaigh
• Server-side: updating keystore? superk888
• WSS4J Encryption with public key ??? superk888
  • RE: WSS4J Encryption with public key ??? Colm O hEigeartaigh
  • RE: WSS4J Encryption with public key ??? superk888
  • Re: WSS4J Encryption with public key ??? Mayank Mishra
• [jira] Created: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Michel Schudel (JIRA)
  • [jira] Updated: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Michel Schudel (JIRA)
  • [jira] Resolved: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Michel Schudel (JIRA)
  • [jira] Commented: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Colm O hEigeartaigh (JIRA)
  • [jira] Commented: (WSS-218) getAliasForX509Cert(String, BigInteger) in CryptoBase returns null if not all aliases are certificates Michel Schudel (JIRA)
• RE: help: directReference, senderVouches & X509Certificate Colm O hEigeartaigh
  • RE: help: directReference, senderVouches & X509Certificate vroom
• how to specify keyInfo content type? vroom
• svn commit: r830515 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/action/ src/org/apache/ws/security/handler/ test/wssec/ coheigea
• svn commit: r830241 - in /webservices/wss4j/trunk: src/org/apache/ws/security/processor/SignatureProcessor.java test/wssec/TestWSSecurityNewSCT.java coheigea
• svn commit: r830233 - in /webservices/wss4j/branches/1_5_x-fixes: src/org/apache/ws/security/processor/SignatureProcessor.java test/wssec/TestWSSecurityNewSCT.java coheigea
• [jira] Created: (WSS-216) SignatureProcessor does not support directly referencing a SecurityContextToken Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-216) SignatureProcessor does not support directly referencing a SecurityContextToken Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-216) SignatureProcessor does not support directly referencing a SecurityContextToken Colm O hEigeartaigh (JIRA)
• svn commit: r830153 - /webservices/wss4j/trunk/src/org/apache/ws/security/processor/SignatureProcessor.java coheigea
• svn commit: r830151 - /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security/processor/SignatureProcessor.java coheigea
• [jira] Created: (WSS-215) SignatureProcessor is not reusing results from WSDocInfo for the Reference case. Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-215) SignatureProcessor is not reusing results from WSDocInfo for the Reference case. Colm O hEigeartaigh (JIRA)
  • [jira] Closed: (WSS-215) SignatureProcessor is not reusing results from WSDocInfo for the Reference case. Colm O hEigeartaigh (JIRA)
• svn commit: r829117 - in /webservices/wss4j/branches/1_5_x-fixes/src/org/apache/ws/security/processor: BinarySecurityTokenProcessor.java DerivedKeyTokenProcessor.java SignatureProcessor.java coheigea
• [jira] Created: (WSS-214) SignatureProcessor is not reusing results from BinarySecurityTokenProcessor or DerivedKeyTokenProcessor Colm O hEigeartaigh (JIRA)
  • [jira] Resolved: (WSS-214) SignatureProcessor is not reusing results from BinarySecurityTokenProcessor or DerivedKeyTokenProcessor Colm O hEigeartaigh (JIRA)

• Earlier messages
• Later messages