Great..! Thanks Amila for taking all the pain in this migration... +1 for the refactoring and code cleanup..once that is done I will merge Kerberos related code to the rampart trunk to work with wss4j 1.6
Thanks & regards, -Prabath On Saturday, February 4, 2012, Amila Jayasekara <ami...@wso2.com> wrote: > On Tue, Jan 24, 2012 at 11:44 AM, Amila Jayasekara <ami...@wso2.com> wrote: >> Following is a status update on this task. >> >> On Wed, Jan 4, 2012 at 4:53 PM, Andreas Veithen >> <andreas.veit...@gmail.com> wrote: >>> On Tue, Jan 3, 2012 at 08:56, Amila Jayasekara <ami...@wso2.com> wrote: >>>> Hi All, >>>> >>>> Current Rampart trunk uses WSS4j 1.5.13. But WSS4J 1.6.4 is available >>>> with more features and bug fixes. It will add a great value to Rampart >>>> if we can migrate to WSS4J 1.6.4. Therefore we are working on >>>> upgrading WSS4J version to 1.6.4. We are planning to do this in >>>> following steps, >>>> >>>> 1. Upgrade OpenSAML version in Rampart trunk. Rampart currently uses >>>> both 1.1 and 2.2.3. We need to upgrade OpenSAML version to 2.5.1-1. >>>> This is the opensaml version used by WSS4J. >> >> This is completed. Changes are commited to trunk and all integration >> tests and unit tests are also passing. Please refer [1] for more >> information. >> >>>> 2. Upgrade WSS4J version in trunk to 1.6.4, with minimum code changes. >>>> Objective of this step is to upgrade WSS4J version of Rampart and make >>>> sure all existing unit tests pass. > > Hi All, > > WSS4J 1.6.4 migration is completed. Spent considerable amount of time > fixing issues in tests. All unit tests and integration tests > successfully executed and all passed. Now Rampart trunk only depends > on WSS4J 1.6.4 and opensaml 2.5.1-1. > Next step would be cleaning up the code. During this step we are > planning to do the following; > - Complete TODO's in code > - Re-factor code in such a way we can add more unit tests > - Add more unit tests > - Add more integration tests > - Improve error handling > - Improve WSS4J/OpenSAML API calls (if possible) > - Re-factor code to reduce duplication > - Fix Javadocs > > We are planning to start code cleaning, with rampart-trust module. I > will create Jira Tickets appropriately, as we proceed. > > With WSS4J migration some interface code has changed. > E.g :- Methods in org.apache.ws.security.WSPasswordCallback class. > pc.getIdentifer() has changed to pc.getIdentifier() > > Due to above, following downstream project builds got broken. I have > attached patches to relevant projects to fix these issues. > > Sandesha 2 – Fixed issues and attached a patch to Jira ticket [1]. > Synapse – Fixed issues and attached a patch to Jira ticket [2] > > [1] https://issues.apache.org/jira/browse/SANDESHA2-211 > [2] https://issues.apache.org/jira/browse/SYNAPSE-840 > > > Thank you, > AmilaJ > >> >> Thanks >> AmilaJ >> >>>> 3. Change Rampart code to use new WSS4J 1.6.4 API's and features and >>>> stabilize the code. This includes SAML2 features and Kerberos >>>> features. >>>> 4. Add more integration tests. >>>> >>>> As mentioned above we are planning to do above changes in trunk it >>>> self. >>> >>> Note that you also have the option to do the changes on a branch >>> (specifically created for that purpose) and to reintegrate them into >>> the trunk once they are stabilized. This frees you from the >>> requirement to keep the code buildable, i.e. you can check in partial >>> changes, even if they temporarily break the build or the tests. This >>> may be interesting if you need to get feedback/contributions from >>> other developers. If you use the corresponding Subversion features >>> correctly, then maintaining such a branch doesn't add much overhead. >>> >>>> The current Rampart releases (1.6.x) will remain supporting >>>> WSS4J 1.5.x. >>>> Relevant Jiras for OpenSAML and WSS4J version upgrades are stated in >>>> [1] and [2]. Will create Jiras for new features as we proceed with >>>> changes. >>>> >>>> Comments/Feedback and Objections are welcome on above approach. >>>> >>>> [1] https://issues.apache.org/jira/browse/RAMPART-354 >>>> [2] https://issues.apache.org/jira/browse/RAMPART-355 >>>> >>>> Thank you >>>> Regards, >>>> AmilaJ >>>> >>>> -- >>>> Mobile : +94773330538 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >>>> For additional commands, e-mail: java-dev-h...@axis.apache.org >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >>> For additional commands, e-mail: java-dev-h...@axis.apache.org >>> >> >> >> >> -- >> Mobile : +94773330538 > > > > -- > Mobile : +94773330538 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > -- Thanks & Regards, Prabath Mobile : +94 71 809 6732 http://blog.facilelogin.com http://RampartFAQ.com
