Hi Milinda,
Good work.
So this requires changes to the policy configurations and thus for
Rampart/C samples I guess.
As you may aware, right now we are holding the Ramaprt/C 1.2.0 until the
corresponding Axis2/C version to be released. We have tested RC1[1] of
Rampart/C 1.2.0 with the Axis2/C 1.3.1 artifacts[2]. Still I did not
start the for Rampart/C as the Axis2/C 1.3.1 is not yet released (Due to
some problems with libxml2).
So is it possible to hold the commits till we release Ramaprt/C 1.2.0.
Cheers,
Kaushalye
[1]http://people.apache.org/~kaushalye/release/rampart-c/1.2.0-RC1/
[2]http://people.apache.org/~dinesh/release/Axis2C-1.3.1/
<http://people.apache.org/%7Edinesh/release/Axis2C-1.3.1/>
Milinda Pathirage wrote:
Hi all,
We have finished implementing PKCS12 Key Store support for Rampart/C. Now we
can use key stores instead of separate certificate and key files. We have
tested all the secpolicy samples and all of them are working fine with
current key manager changes and key store support. Rampart/C with pkcs12 and
new key manager implementation is available in pkcs folder under Rampart/C
scratch.
I think, we can move this new implementation to Rampart/C trunk. What is
your idea about this. Please feel free to comment on this.
Thanks
Milinda
--
http://blog.kaushalye.org/
http://wso2.org/
