All Projects : Rampart (Key: RAMPART)

Project Lead: Ruchith Udayanga Fernando
URL: http://ws.apache.org/rampart/
Description:
WS-Security and Trust implementation for Axis2

Release Notes

Road Map View personal road map Scope: next 3 versions | all versions 1.5 ( Release Notes ) Progress:    23 of 26 issues have been resolved Apache Rampart release for Apache Axis2-1.5    RAMPART-258 UNRESOLVED A sample is required to demonstrate the SAML 2.0 Token issuing capability in Rampart    RAMPART-259 UNRESOLVED SAML2TokenIssuer calls DefaultBootstrap.bootstrap() per every request and attribute call back handler not being called    RAMPART-262 UNRESOLVED SymmetricBinding client can invoke the AsymmetricBinding service policy    RAMPART-193 FIXED Missing signature in SOAP fault messages    RAMPART-191 FIXED NullPointerException in AbstractHTTPSender.java:126 leading to "Unexpected number of certificates: 0"    RAMPART-255 FIXED Sample05 does not work correctly    RAMPART-260 FIXED Sample06 does not work correctly    RAMPART-189 FIXED WS-Security rampart uses wrong token in service response    RAMPART-257 FIXED "build.xml" file inside the samples/policy does not copy the correct versions of the rampart, rahas, and addressing mar files.    RAMPART-251 FIXED <EncryptedElements/> fails when the element is not namespce qualified    RAMPART-248 FIXED Caching crypto objects to improve the performance when using the same crypto for signing and encrypting.    RAMPART-250 FIXED For SecureConversationToken key identifier type not set properly    RAMPART-244 FIXED Invalid behavior when empty <sp:EncryptedParts/> element present in the policy    RAMPART-246 FIXED Need to able to set a AttributeCallbackHandler class by name to the SAMLTokenIssuerConfig    RAMPART-232 FIXED Problem when body is signed and then an XPath is encrypted    RAMPART-200 FIXED Provide capability to configure x509 supporting token certificates different from the ones used for the assymetric binding    RAMPART-230 FIXED Rampart expands message object model unnecessarily    RAMPART-247 FIXED Rampart fails to handle scenarios where password type is not set by default in UsernameToken [where 'type' is not included in the UsernameToken element]    RAMPART-256 FIXED Sample for a policy having multiple supporting tokens - enabling to sign/encrypt with multiple keys    RAMPART-245 FIXED Supporting same type of multiple SupprtingToken    RAMPART-233 FIXED Tests are required for negative scenario testing    RAMPART-249 FIXED The way attached references and unattached references created incorrectly for SAML tokens and does not interop with WCF    RAMPART-243 FIXED Updating the README.txt and the contents of the binary distribution corresponding to SAML 2.0 support    RAMPART-209 FIXED https urls are present in the src checkout page for both anonymous and developpers    RAMPART-231 FIXED Implementing the SAML 2.0 support in Rampart    RAMPART-242 FIXED Test Cases are required for upcoming SAML2.0 support in Rampart

Reports

Preset Filters

Project Summary

	Open	93	35%
	In Progress	1
	Reopened	1
	Resolved	153	57%
	Closed	19	7%

Open Issues

	Critical	4	4%
	Major	73	77%
	Minor	18	19%

By Assignee

Dimuthu Leelarathne	2	2%
Nandana Mihindukulasooriya	25	26%
Ruchith Udayanga Fernando	46	48%
Unassigned	22	23%