[jira] Issue Comment Edited: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930666#action_12930666 ] Colm O hEigeartaigh edited comment on WSS-40 at 11/10/10 12:34 PM:

[jira] Updated: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-40: --- Fix Version/s: 1.5.10 WSSecurityEngine does not support chained certificates

[jira] Issue Comment Edited: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930666#action_12930666 ] Colm O hEigeartaigh edited comment on WSS-40 at 11/10/10 12:38 PM:

[jira] Created: (WSS-248) Remove Axis1 artifacts in WSS4J 1.6

Remove Axis1 artifacts in WSS4J 1.6 --- Key: WSS-248 URL: https://issues.apache.org/jira/browse/WSS-248 Project: WSS4J Issue Type: Task Reporter: Colm O hEigeartaigh Assignee: Colm O

[jira] Created: (WSS-249) Parameterize Collections in WSS4J 1.6

Parameterize Collections in WSS4J 1.6 - Key: WSS-249 URL: https://issues.apache.org/jira/browse/WSS-249 Project: WSS4J Issue Type: Task Reporter: Colm O hEigeartaigh Assignee: Colm

[jira] Commented: (WSS-208) Signature or decryption was invalid problem when setting WSDoAllSender properties programmatically (Canonicalization / C14N / SAAJ problem ?)

[ https://issues.apache.org/jira/browse/WSS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931073#action_12931073 ] Colm O hEigeartaigh commented on WSS-208: - I took another look at this issue. The

[jira] Resolved: (WSS-249) Parameterize Collections in WSS4J 1.6

[ https://issues.apache.org/jira/browse/WSS-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-249. - Resolution: Fixed Parameterize Collections in WSS4J 1.6

[jira] Commented: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931461#action_12931461 ] Colm O hEigeartaigh commented on WSS-40: I committed a port to 1_5_x-fixes. I'm going

[jira] Resolved: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-40. Resolution: Fixed WSSecurityEngine does not support chained certificates

[jira] Closed: (WSS-40) WSSecurityEngine does not support chained certificates

[ https://issues.apache.org/jira/browse/WSS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-40. -- WSSecurityEngine does not support chained certificates

[jira] Assigned: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

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

[jira] Commented: (WSS-252) org.apache.ws.security.processor.UsernameTokenProcessor is not thread safe/prone to hacker attacks

[ https://issues.apache.org/jira/browse/WSS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932899#action_12932899 ] Colm O hEigeartaigh commented on WSS-252: - Hi Marek, Could you be more specific

[jira] Updated: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-238: Attachment: wss-238-revised.patch Switch to wsse:KeyIdentifier instead of wsse:Reference for

[jira] Commented: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932977#action_12932977 ] Colm O hEigeartaigh commented on WSS-238: - Hi Glen, Apologies for not looking at

[jira] Updated: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-238: Fix Version/s: 1.5.10 Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML

[jira] Commented: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933394#action_12933394 ] Colm O hEigeartaigh commented on WSS-238: - Hi Glen, Thanks for confirming that the

[jira] Issue Comment Edited: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933394#action_12933394 ] Colm O hEigeartaigh edited comment on WSS-238 at 11/18/10 6:29 AM:

[jira] Closed: (WSS-247) Upgrade to XML Security 1.4.4

[ https://issues.apache.org/jira/browse/WSS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-247. --- Upgrade to XML Security 1.4.4 - Key: WSS-247

[jira] Resolved: (WSS-247) Upgrade to XML Security 1.4.4

[ https://issues.apache.org/jira/browse/WSS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-247. - Resolution: Fixed Upgrade to XML Security 1.4.4 -

[jira] Updated: (WSS-253) UsernameTokenProcessor logs the password to the log

[ https://issues.apache.org/jira/browse/WSS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-253: Fix Version/s: 1.6 1.5.10 I'll just replace logging the password, with

[jira] Commented: (WSS-238) Switch to wsse:KeyIdentifier instead of wsse:Reference for SAML references within SOAP:body EncryptedData elements.

[ https://issues.apache.org/jira/browse/WSS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933801#action_12933801 ] Colm O hEigeartaigh commented on WSS-238: - Thanks for logging that issue with WSIT

[jira] Closed: (WSS-253) UsernameTokenProcessor logs the password to the log

[ https://issues.apache.org/jira/browse/WSS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-253. --- UsernameTokenProcessor logs the password to the log

[jira] Resolved: (WSS-253) UsernameTokenProcessor logs the password to the log

[ https://issues.apache.org/jira/browse/WSS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-253. - Resolution: Fixed UsernameTokenProcessor logs the password to the log

[jira] Created: (WSS-255) Add support for enforcing a text or digest password type when processing a UsernameToken

Add support for enforcing a text or digest password type when processing a UsernameToken Key: WSS-255 URL: https://issues.apache.org/jira/browse/WSS-255

[jira] Created: (WSS-256) Review Basic Security Token and Reliable Secure Profile spec compliance

Review Basic Security Token and Reliable Secure Profile spec compliance --- Key: WSS-256 URL: https://issues.apache.org/jira/browse/WSS-256 Project: WSS4J Issue Type: Task

[jira] Updated: (WSS-256) Review Basic Security Profile and Reliable Secure Profile spec compliance

[ https://issues.apache.org/jira/browse/WSS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-256: Description: This is a task to review the coverage of Basic Security Profile, and Reliable

[jira] Created: (WSS-257) Avoid converting the SOAP Body to DOM on the processing side if possible

Avoid converting the SOAP Body to DOM on the processing side if possible Key: WSS-257 URL: https://issues.apache.org/jira/browse/WSS-257 Project: WSS4J Issue Type:

[jira] Closed: (WSS-248) Remove Axis1 artifacts in WSS4J 1.6

[ https://issues.apache.org/jira/browse/WSS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-248. --- Remove Axis1 artifacts in WSS4J 1.6 --- Key:

[jira] Resolved: (WSS-258) Newer version of SecureConversation not recognised for derived key algorithm

[ https://issues.apache.org/jira/browse/WSS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-258. - Resolution: Fixed Newer version of SecureConversation not recognised for derived key

[jira] Resolved: (WSS-250) Refactor testing

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

[jira] Commented: (WSS-261) Rampart failing to extract keyinfo from SAML assertion

[ https://issues.apache.org/jira/browse/WSS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974133#action_12974133 ] Colm O hEigeartaigh commented on WSS-261: - KeyValue is supported in WSS4J 1.5.9, see

[jira] Assigned: (WSS-261) Rampart failing to extract keyinfo from SAML assertion

[ https://issues.apache.org/jira/browse/WSS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned WSS-261: --- Assignee: Colm O hEigeartaigh (was: Ruchith Udayanga Fernando) Rampart failing to

[jira] Closed: (WSS-261) Rampart failing to extract keyinfo from SAML assertion

[ https://issues.apache.org/jira/browse/WSS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-261. --- Rampart failing to extract keyinfo from SAML assertion

[jira] Closed: (WSS-232) Performance Improvement in WSSConfig

[ https://issues.apache.org/jira/browse/WSS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-232. --- Performance Improvement in WSSConfig Key:

[jira] Resolved: (WSS-232) Performance Improvement in WSSConfig

[ https://issues.apache.org/jira/browse/WSS-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-232. - Resolution: Fixed This is now fixed in 1.6-SNAPSHOT. Thanks for the patch. Colm.

[jira] Commented: (WSS-251) Support WSS Kerberos Token Profile

[ https://issues.apache.org/jira/browse/WSS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12974267#action_12974267 ] Colm O hEigeartaigh commented on WSS-251: - Hi Prabath, Any update on this patch?

[jira] Created: (WSS-262) WSS4J accepts Timestamps that are Created in the future

WSS4J accepts Timestamps that are Created in the future - Key: WSS-262 URL: https://issues.apache.org/jira/browse/WSS-262 Project: WSS4J Issue Type: Bug Components: WSS4J

[jira] Resolved: (WSS-262) WSS4J accepts Timestamps that are Created in the future

[ https://issues.apache.org/jira/browse/WSS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-262. - Resolution: Fixed WSS4J accepts Timestamps that are Created in the future

[jira] Closed: (WSS-262) WSS4J accepts Timestamps that are Created in the future

[ https://issues.apache.org/jira/browse/WSS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-262. --- WSS4J accepts Timestamps that are Created in the future

[jira] Updated: (WSS-146) Upgrade opensaml dependency to 2.x line

[ https://issues.apache.org/jira/browse/WSS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-146: Attachment: saml_port.patch.2 Here's the first (non-compiling) draft of porting trunk to use

[jira] Created: (WSS-263) Store secret key from signature processor

Store secret key from signature processor - Key: WSS-263 URL: https://issues.apache.org/jira/browse/WSS-263 Project: WSS4J Issue Type: Improvement Components: WSS4J Axis Integration

[jira] Updated: (WSS-263) Store secret key from signature processor

[ https://issues.apache.org/jira/browse/WSS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-263: Fix Version/s: 1.6 Store secret key from signature processor

[jira] Closed: (WSS-263) Store secret key from signature processor

[ https://issues.apache.org/jira/browse/WSS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-263. --- Store secret key from signature processor -

[jira] Resolved: (WSS-263) Store secret key from signature processor

[ https://issues.apache.org/jira/browse/WSS-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-263. - Resolution: Fixed Store secret key from signature processor

[jira] Created: (WSS-266) Provide better support for pluggable authentication/verification of security tokens

Provide better support for pluggable authentication/verification of security tokens --- Key: WSS-266 URL: https://issues.apache.org/jira/browse/WSS-266 Project: WSS4J

[jira] Closed: (WSS-146) Upgrade opensaml dependency to 2.x line

[ https://issues.apache.org/jira/browse/WSS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-146. --- Upgrade opensaml dependency to 2.x line ---

[jira] Resolved: (WSS-146) Upgrade opensaml dependency to 2.x line

[ https://issues.apache.org/jira/browse/WSS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-146. - Resolution: Fixed Upgrade opensaml dependency to 2.x line

[jira] Updated: (WSS-251) Support WSS Kerberos Token Profile

[ https://issues.apache.org/jira/browse/WSS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-251: Fix Version/s: (was: 1.6) As I've received no patch for this issue, I'm removing the

[jira] Commented: (WSS-146) Upgrade opensaml dependency to 2.x line

[ https://issues.apache.org/jira/browse/WSS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990039#comment-12990039 ] Colm O hEigeartaigh commented on WSS-146: - Do you have a sense of when v 1.6 will

[jira] Commented: (WSS-266) Provide better support for pluggable authentication/verification of security tokens

[ https://issues.apache.org/jira/browse/WSS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12990589#comment-12990589 ] Colm O hEigeartaigh commented on WSS-266: - The implementation I ended up with is

[jira] Updated: (WSS-265) Test EncryptedKey elements in the Subject in a SAML Assertion

[ https://issues.apache.org/jira/browse/WSS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-265: Fix Version/s: (was: 1.6) 1.6.1 Moving to 1.6.1 as it doesn't appear

[jira] Closed: (WSS-266) Provide better support for pluggable authentication/verification of security tokens

[ https://issues.apache.org/jira/browse/WSS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-266. --- Provide better support for pluggable authentication/verification of security tokens

[jira] Closed: (WSS-271) Add support for custom validation of BinarySecurityTokens

[ https://issues.apache.org/jira/browse/WSS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-271. --- Add support for custom validation of BinarySecurityTokens

[jira] Resolved: (WSS-252) org.apache.ws.security.processor.UsernameTokenProcessor is not thread safe/prone to hacker attacks

[ https://issues.apache.org/jira/browse/WSS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-252. - Resolution: Won't Fix org.apache.ws.security.processor.UsernameTokenProcessor is not

[jira] Resolved: (WSS-228) Encryption with a UsernameToken is (almost) broken

[ https://issues.apache.org/jira/browse/WSS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-228. - Resolution: Won't Fix Marking as won't fix due to lack of information. Encryption with a

[jira] Updated: (WSS-254) Encryption/signing of multiple message parts with same name not working

[ https://issues.apache.org/jira/browse/WSS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-254: Fix Version/s: 1.6 Encryption/signing of multiple message parts with same name not working

[jira] Created: (WSS-272) STR Transform must contain an InclusiveNamespaces child as per the BSP spec

STR Transform must contain an InclusiveNamespaces child as per the BSP spec --- Key: WSS-272 URL: https://issues.apache.org/jira/browse/WSS-272 Project: WSS4J Issue

[jira] Commented: (WSS-254) Encryption/signing of multiple message parts with same name not working

[ https://issues.apache.org/jira/browse/WSS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12997340#comment-12997340 ] Colm O hEigeartaigh commented on WSS-254: - Hi Marcin, I don't view it as the job of

[jira] Resolved: (WSS-269) Refactor the Crypto interface

[ https://issues.apache.org/jira/browse/WSS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-269. - Resolution: Fixed Refactor the Crypto interface -

[jira] Closed: (WSS-269) Refactor the Crypto interface

[ https://issues.apache.org/jira/browse/WSS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-269. --- Refactor the Crypto interface - Key: WSS-269

[jira] Commented: (WSS-273) org.apache.ws.security.transform.STRTransform causes ClassCastException when wss4j is running on IBM 1.6 JVM

[ https://issues.apache.org/jira/browse/WSS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12999432#comment-12999432 ] Colm O hEigeartaigh commented on WSS-273: - Hi, Thanks for testing the alpha release.

[jira] Updated: (WSS-264) OSGi bundle should NOT specify the universal DynamicImport-Package: *

[ https://issues.apache.org/jira/browse/WSS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-264: Fix Version/s: (was: 1.5.12) OSGi bundle should NOT specify the universal

[jira] Resolved: (WSS-264) OSGi bundle should NOT specify the universal DynamicImport-Package: *

[ https://issues.apache.org/jira/browse/WSS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-264. - Resolution: Fixed Fixed for 1.6 - I'm leaving the 1.5.x branch alone for backwards

[jira] Resolved: (WSS-256) Review Basic Security Profile and Reliable Secure Profile spec compliance

[ https://issues.apache.org/jira/browse/WSS-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-256. - Resolution: Fixed Review Basic Security Profile and Reliable Secure Profile spec

[jira] Resolved: (WSS-274) Add support for allowing future-dated Timestamps

[ https://issues.apache.org/jira/browse/WSS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-274. - Resolution: Fixed Add support for allowing future-dated Timestamps

[jira] Closed: (WSS-274) Add support for allowing future-dated Timestamps

[ https://issues.apache.org/jira/browse/WSS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-274. --- Add support for allowing future-dated Timestamps

[jira] Resolved: (WSS-268) Upload Opensaml2 artifacts, and dependencies, to Maven Central

[ https://issues.apache.org/jira/browse/WSS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-268. - Resolution: Fixed The Opensaml2 artifacts are now in Maven Central:

[jira] [Created] (WSS-275) Use SLF4J for logging framework for 1.6

Use SLF4J for logging framework for 1.6 --- Key: WSS-275 URL: https://issues.apache.org/jira/browse/WSS-275 Project: WSS4J Issue Type: Improvement Reporter: Colm O hEigeartaigh

[jira] [Updated] (WSS-275) Use SLF4J for logging framework for 1.6

[ https://issues.apache.org/jira/browse/WSS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-275: Fix Version/s: (was: 1.6) 1.6.1 Bumping this to 1.6.1 to allow more

[jira] [Closed] (WSS-257) Avoid converting the SOAP Body to DOM on the processing side if possible

[ https://issues.apache.org/jira/browse/WSS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-257. --- Avoid converting the SOAP Body to DOM on the processing side if possible

[jira] [Closed] (WSS-254) Encryption/signing of multiple message parts with same name not working

[ https://issues.apache.org/jira/browse/WSS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed WSS-254. --- Encryption/signing of multiple message parts with same name not working

[jira] [Created] (WSS-276) Support signing a SAML Assertion using a derived key

Support signing a SAML Assertion using a derived key Key: WSS-276 URL: https://issues.apache.org/jira/browse/WSS-276 Project: WSS4J Issue Type: Bug Affects Versions: 1.6

[jira] [Resolved] (WSS-276) Support signing a SAML Assertion using a derived key

[ https://issues.apache.org/jira/browse/WSS-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-276. - Resolution: Fixed Support signing a SAML Assertion using a derived key

[jira] [Commented] (WSS-279) WSPasswordCallback method getPasswordType() was removed in 1.6.0 without being deprecated in 1.5.11.

[ https://issues.apache.org/jira/browse/WSS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021597#comment-13021597 ] Colm O hEigeartaigh commented on WSS-279: - Lots of things have been removed in 1.6.0

[jira] [Issue Comment Edited] (WSS-279) WSPasswordCallback method getPasswordType() was removed in 1.6.0 without being deprecated in 1.5.11.

[ https://issues.apache.org/jira/browse/WSS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13021597#comment-13021597 ] Colm O hEigeartaigh edited comment on WSS-279 at 4/20/11 10:09 AM:

[jira] [Commented] (WSS-279) WSPasswordCallback method getPasswordType() was removed in 1.6.0 without being deprecated in 1.5.11.

[ https://issues.apache.org/jira/browse/WSS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022061#comment-13022061 ] Colm O hEigeartaigh commented on WSS-279: - I assume you're talking about the

[jira] [Commented] (WSS-277) can't get all certificates from Crypto

[ https://issues.apache.org/jira/browse/WSS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022108#comment-13022108 ] Colm O hEigeartaigh commented on WSS-277: - What is the use-case you have for wanting

[jira] [Commented] (WSS-273) org.apache.ws.security.transform.STRTransform causes ClassCastException when wss4j is running on IBM 1.6 JVM

[ https://issues.apache.org/jira/browse/WSS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026196#comment-13026196 ] Colm O hEigeartaigh commented on WSS-273: - Hi Jeremy, Rather than change the

[jira] [Resolved] (WSS-280) USE_DERIVED_KEY instead of USE_DERIVED_KEY_FOR_MAC in WSHandler

[ https://issues.apache.org/jira/browse/WSS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-280. - Resolution: Fixed USE_DERIVED_KEY instead of USE_DERIVED_KEY_FOR_MAC in WSHandler

[jira] [Resolved] (WSS-275) Use SLF4J for logging framework for 1.6

[ https://issues.apache.org/jira/browse/WSS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-275. - Resolution: Won't Fix I decided not to proceed with this issue, for reasons outlined on

[jira] [Commented] (WSS-277) can't get all certificates from Crypto

[ https://issues.apache.org/jira/browse/WSS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13027007#comment-13027007 ] Colm O hEigeartaigh commented on WSS-277: - Hi Marcin, I'm not inclined to add

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

[ https://issues.apache.org/jira/browse/WSS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13028137#comment-13028137 ] Colm O hEigeartaigh commented on WSS-281: - This is not a bug. The job of the password

[jira] [Resolved] (WSS-283) ClassCastException when signing message with existing WSSE header containing Text as first child

[ https://issues.apache.org/jira/browse/WSS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-283. - Resolution: Fixed ClassCastException when signing message with existing WSSE header

[jira] [Resolved] (WSS-285) Error in SAML1.1 Conditions support

[ https://issues.apache.org/jira/browse/WSS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-285. - Resolution: Fixed Error in SAML1.1 Conditions support ---

[jira] [Updated] (WSS-278) verifyTrust in Crypto should use CRLs as well

[ https://issues.apache.org/jira/browse/WSS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-278: Affects Version/s: (was: 1.6.1) Fix Version/s: 1.6.1 verifyTrust in Crypto

[jira] [Updated] (WSS-273) org.apache.ws.security.transform.STRTransform causes ClassCastException when wss4j is running on IBM 1.6 JVM

[ https://issues.apache.org/jira/browse/WSS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-273: Attachment: wss4j-1.6.1-SNAPSHOT.jar Hi all, Could you try the attached 1.6.1-SNAPSHOT jar

[jira] [Commented] (WSS-282) STRTransform JCE provider throws java.lang.ClassCastException: org.jcp.xml.dsig.internal.dom.DOMSubTreeData incompatible with javax.xml.crypto.OctetStreamData in Webspher

[ https://issues.apache.org/jira/browse/WSS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035252#comment-13035252 ] Colm O hEigeartaigh commented on WSS-282: - Note the comment on WSS-273:

[jira] [Updated] (WSS-282) STRTransform JCE provider throws java.lang.ClassCastException: org.jcp.xml.dsig.internal.dom.DOMSubTreeData incompatible with javax.xml.crypto.OctetStreamData in Websphere

[ https://issues.apache.org/jira/browse/WSS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-282: Fix Version/s: 1.6.1 STRTransform JCE provider throws java.lang.ClassCastException:

[jira] [Updated] (WSS-273) org.apache.ws.security.transform.STRTransform causes ClassCastException when wss4j is running on IBM 1.6 JVM

[ https://issues.apache.org/jira/browse/WSS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-273: Fix Version/s: 1.6.1 org.apache.ws.security.transform.STRTransform causes ClassCastException

[jira] [Resolved] (WSS-273) org.apache.ws.security.transform.STRTransform causes ClassCastException when wss4j is running on IBM 1.6 JVM

[ https://issues.apache.org/jira/browse/WSS-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-273. - Resolution: Fixed Marking this as resolved. I'll leave WSS-282 open for the time being.

[jira] [Commented] (WSS-286) Evidence element not present in SAML AuthzDecisionStatement

[ https://issues.apache.org/jira/browse/WSS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036734#comment-13036734 ] Colm O hEigeartaigh commented on WSS-286: - Hi David, Could you create a patch and

[jira] [Issue Comment Edited] (WSS-286) Evidence element not present in SAML AuthzDecisionStatement

[ https://issues.apache.org/jira/browse/WSS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13036734#comment-13036734 ] Colm O hEigeartaigh edited comment on WSS-286 at 5/20/11 9:25 AM:

[jira] [Updated] (WSS-288) Incorporating Colm's Blog entries into WSS4J documentation

[ https://issues.apache.org/jira/browse/WSS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-288: Fix Version/s: 1.6.1 Incorporating Colm's Blog entries into WSS4J documentation

[jira] [Resolved] (WSS-288) Incorporating Colm's Blog entries into WSS4J documentation

[ https://issues.apache.org/jira/browse/WSS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-288. - Resolution: Fixed The changes are now live on the website. Colm. Incorporating Colm's

[jira] [Updated] (WSS-265) Test EncryptedKey elements in the Subject in a SAML Assertion

[ https://issues.apache.org/jira/browse/WSS-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-265: Fix Version/s: (was: 1.6.1) 1.6.2 Moving this to 1.6.2 as Opensaml

[jira] [Resolved] (WSS-278) verifyTrust in Crypto should use CRLs as well

[ https://issues.apache.org/jira/browse/WSS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-278. - Resolution: Fixed Fixed. Please see this blog entry for more details:

[jira] [Commented] (WSS-289) Text improvements to website pages

[ https://issues.apache.org/jira/browse/WSS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041496#comment-13041496 ] Colm O hEigeartaigh commented on WSS-289: - Could you re-attach the patch granting

[jira] [Created] (WSS-290) Create Principals when processing SAML and BinarySecurityTokens

Create Principals when processing SAML and BinarySecurityTokens --- Key: WSS-290 URL: https://issues.apache.org/jira/browse/WSS-290 Project: WSS4J Issue Type: Improvement

[jira] [Updated] (WSS-290) Create Principals when processing SAML and BinarySecurityTokens

[ https://issues.apache.org/jira/browse/WSS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated WSS-290: Description: This task involves creating Principals when processing SAML and

[jira] [Resolved] (WSS-289) Text improvements to website pages

[ https://issues.apache.org/jira/browse/WSS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved WSS-289. - Resolution: Fixed Text improvements to website pages --

  1   2   3   4   5   6   7   8   9   10   >