You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by na...@apache.org on 2008/05/28 04:37:33 UTC
svn commit: r660791 -
/webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt
Author: nandana
Date: Tue May 27 19:37:33 2008
New Revision: 660791
URL: http://svn.apache.org/viewvc?rev=660791&view=rev
Log:
Change log for rampart version
Added:
webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt
Added: webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt
URL: http://svn.apache.org/viewvc/webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt?rev=660791&view=auto
==============================================================================
--- webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt (added)
+++ webservices/rampart/branches/java/1_4/release-docs/ChangeLog.txt Tue May 27 19:37:33 2008
@@ -0,0 +1,134 @@
+This file contains a listing of all Jira issues that have been closed
+for a given release.
+
+Release 1.4
+===========
+
+** Bug
+ * [RAMPART-41] - "IncludeToken/Once" is not handled properly in Rampart
+ * [RAMPART-84] - "SupportingTokens" Token Inop for Asymetric Binding (Sign before Encrypt)
+ * [RAMPART-86] - Test the SymmetricBinding implementation
+ * [RAMPART-88] - Policy sample "sample-tomcat" incorrectly adds client.jks to Client's truststore
+ * [RAMPART-89] - License files missing in distribution
+ * [RAMPART-90] - Rampart must respond using the applicable WS-Policy even when returning a fault
+ * [RAMPART-91] - Wrong KeyIdentifierType in WSSecSignature and WSSecEncryptedKey
+ * [RAMPART-92] - Error in checking generated encrypted parts with the policy
+ * [RAMPART-93] - ValueType is not set correctly in the Signature when a encrypted key is used to sign
+ * [RAMPART-100] - Missing encrypted key token in response when Asymmetric Binding is used
+ * [RAMPART-101] - Rampart uses xmlsec-1.4.0
+ * [RAMPART-102] - Policy Validation Error
+ * [RAMPART-104] - Rampart generates empty reference lists
+ * [RAMPART-107] - Rampart ignores the MTOM assertion in the bootstrap policy in secure conversation
+ * [RAMPART-108] - Policy Validator doesn't check the transport when Transport binding is used with HttpsToken
+ * [RAMPART-109] - Error in placement of reference list in No-Timestamp scenarios
+ * [RAMPART-110] - Symmetric binding scenario: "Cannot find Reference in Manifest" Exception is thrown
+ * [RAMPART-114] - "Unexpected signature" exception thrown when using Signed/SupportingTokens Assertion
+ * [RAMPART-115] - Incrorrect reference URI in the soap response in Secure Conversation Scenarios
+ * [RAMPART-117] - 1.3 not available on download page
+ * [RAMPART-122] - /sp:EncryptedParts/sp:Header needs qualified attribute names
+ * [RAMPART-123] - client stub are not given the namespace declaration for <sp:EncryptedElements>
+ * [RAMPART-124] - /sp:SignedParts/sp:Header selects no elements if the Name attribute is unspecified
+ * [RAMPART-125] - Encryption of SOAP Headers broken
+ * [RAMPART-127] - Possible Security Hole
+ * [RAMPART-129] - Validation of supporting tokens according to a service's policy
+ * [RAMPART-130] - MTOM with WS-Security
+ * [RAMPART-131] - Rampart security header problem
+ * [RAMPART-132] - Issue with XPath configuration inside RampartUtil
+ * [RAMPART-133] - Supporting tokens are not added to the soap header
+ * [RAMPART-136] - Rampart doesn't support RequiredElements Assertion
+ * [RAMPART-138] - Created response of SymmetricBindingBuilder WITHOUT timestamp is incorrect
+ * [RAMPART-139] - SignatureToken doesn't work for Symetricbinding
+ * [RAMPART-140] - Processing of response fails if a security policy is set
+ * [RAMPART-141] - Issue of Rampart not supporting X509PKIPathv1 token
+ * [RAMPART-143] - Policy with 'Layout' 'Lax' having no subelements leads to a NullPointerException in PolicyEngine
+ * [RAMPART-145] - When we use an issued token for sig/encrypt we must use the attached reference or unattached reference as specified by policy
+ * [RAMPART-146] - The exact elements that are equired to be encrypted are not validated
+ * [RAMPART-147] - Header parts included in EncryptedParts are not processed by Rampart
+ * [RAMPART-148] - Release notes are not copied to source distribution
+ * [RAMPART-149] - Improvements to the documentation
+ * [RAMPART-151] - Rahas docs not being built
+ * [RAMPART-153] - Incorrect links given in source checkout page
+ * [RAMPART-157] - Duplicate namespace declaration in SingedEncryptedElements assertion
+ * [RAMPART-160] - Source files are also copied in to Rampart jars
+ * [RAMPART-161] - java.util.ConcurrentModificationException while a token is associated with a user when sevaral users are using a service
+ * [RAMPART-162] - NullPointerException thrown when a non-existing algorythm suite is used in a policy file when invoking a secured service
+ * [RAMPART-165] - Exception in Rampart Processing causes NPE
+ * [RAMPART-166] - Wrong SoapFault code accessing a Secure endpoint without security
+ * [RAMPART-167] - Remove bouncycastle from the distribution and add a note
+ * [RAMPART-168] - When SecureConversationTokens are used Rampart always try to use the attached reference
+ * [RAMPART-169] - HttpsToken serializer does not support ws-securitypolicy 1.2
+
+** Improvement
+ * [RAMPART-85] - Uncommented and fixed AsymmetricBindingBuilderTest
+ * [RAMPART-94] - Change rampart implementation to use same encrypted key in both request and response messages
+ * [RAMPART-99] - add userCertAlias parameter to Rampart Configuration
+ * [RAMPART-103] - include a note on adding bouncycastle as a security provider in the JRE
+ * [RAMPART-105] - Update RampartTest to include test scenarios for RAMPART-99, RAMPART-102 and RAMPART-104
+ * [RAMPART-106] - Encrypt the Username Token when it is used as a supporting token
+ * [RAMPART-113] - Enforce transport level security when Transport binding is used with Https Token
+ * [RAMPART-120] - sources unavailable in maven repository
+ * [RAMPART-134] - Add WS - Security Policy 1.2 support to Rampart
+ * [RAMPART-135] - Allow custom implementation of PolicyBasedResultsValidator using callback handler mechanism
+ * [RAMPART-137] - Add tests for encrypted supporting token scenarios
+ * [RAMPART-152] - Timestamp Precision In Milliseconds Configuration
+ * [RAMPART-163] - Update the WS wiki with Rampart information
+
+** New Feature
+ * [RAMPART-87] - Add renewal and validation support for issued token
+ * [RAMPART-95] - Support Encrypted Header
+
+
+
+** Task
+ * [RAMPART-158] - Create a FAQ
+ * [RAMPART-159] - Fix Releases/Versions in Rampart JIRA
+
+Release 1.3 - 06/Sep/07
+=======================
+
+** Bug
+ * [RAMPART-32] - Processing of <Issuer> and <RequestSecurityTokenTemplate> in class org.apache.ws.secpolicy.builders.IssuedTokenBuilder is wrong.
+ * [RAMPART-42] - TransportBinding does not encrypt the message payload
+ * [RAMPART-49] - RampartPolicyBuilder logs to console/System.out
+ * [RAMPART-52] - UsernameToken Builder Bug.
+ * [RAMPART-53] - rampart causes problems with hierarchies
+ * [RAMPART-57] - Move generated code into target directory in rampart-integration test
+ * [RAMPART-58] - problems engaging rampart per operation
+ * [RAMPART-62] - Build failure on Mac OS
+ * [RAMPART-76] - Rampart 1.3.mar throws error with Axis2 1.3
+ * [RAMPART-79] - setAction in Options does not create a non-null "Action" element in the SOAP Header
+
+** Improvement
+ * [RAMPART-17] - Create Apache Rampart website
+ * [RAMPART-20] - Improve logging
+ * [RAMPART-27] - The user in the configuration for UsernameToken and Signature should be different
+ * [RAMPART-48] - RampartMessageData class needs tightening
+ * [RAMPART-51] - Rampart developer guide
+ * [RAMPART-54] - Reviewed the Developer Guide
+
+Release 1.2 - 02/Jun/07
+=======================
+
+** Bug
+ * [RAMPART-12] - ClassCastException in fault parsing
+ * [RAMPART-28] - Cannot add parts of the header for encryption
+ * [RAMPART-34] - SignedEncryptedSupportingTokens assertion does not work
+ * [RAMPART-35] - SignedSupportingTokens does not sign the UsernameToken
+ * [RAMPART-36] - Using the "SupportingTokens" assertion throws exception
+ * [RAMPART-37] - SymmetricBinding is broken
+ * [RAMPART-43] - When IncludeTimestamp is commented in Sample03 service throws a Nullpointer exception.
+
+
+** New Feature
+ * [RAMPART-38] - AsymmetricBinding does not support UsernameToken as a supporting token
+ * [RAMPART-40] - implementation of the Xpath support
+
+
+
+
+
+
+
+
+
+