Hi Thilina,
So in policy.xml of sample 4, there are few parameters like, user,
encryptionUser, passwordCallbackClass, signatureCrypto and encryptionCrypto.
In my understanding, the signatureCrypto and encryptionCrypto are required
for mentioning the keystore and its username, password, right ? An
Hi,
The issue is with the RampartConfig assertion of the policy. In Rampart
Java, it is required to provide a different set of parameters in the
RampartConfig assertion.
A scenario similar to your case is covered in Rampart sample-04. This is
available in standard Rampart binary distribution
(ram
I guess the email text didn't appear in my last email although the files
that I wanted to send did appear ... so sending the message again ..
Here is the scenario:
[Note: I had to sanitize the files a little bit that I have attached here
due to proprietary reasons but I made sure that the concep
I guess the email text didnt appear in my last email although the files that
I wanted to send did appear ... so sending the message again ..
Thanks a lot for taking a look at this ...
>
> Here is the scenario:
>
> [Note: I had to sanitize the files a little bit that I have attached here
> due to
Hi Thilina,
Thanks a lot for taking a look at this ...
Here is the scenario:
[Note: I had to sanitize the files a little bit that I have attached here
due to proprietery reasons but I made sure that the conceptually nothing is
changed.]
So At Server side, there are couple of files:
1) server_s
If you can share the complete policy/scenario with us, then it would be much
easier to point you to an equivalent rampart config.
Thanks,
Thilina
On Thu, Feb 17, 2011 at 11:29 PM, Devdatta Lele wrote:
> Hi I have RampartConfig used in Axis2C as follows:
>
> http://ws.apache.org/rampart/c/policy"
