Re: +Rampart Sign with two Certificates

2009-10-14 Thread m4rkuz
Thanks Prabath,

I apologize for my English or my description, I see now it was misleading,
and thanks for the clarification, I have now a preliminary demo working
fine, the thing was I thought I need to specify two users in my policy file,
but after importing the public key of my server into my client it start to
work fine

Thanks Again,

Marcus


___
Marcus Sánchez Díaz.
Enterprise Developer.
SCJP - SCWCD.


On Wed, Oct 14, 2009 at 4:53 PM, Prabath Siriwardena wrote:

> Hi Marcus;
>
> The 'subject' of the mail doesn't seem to reflect the same in the
> 'description' of the mail - if I understood correctly...
>
> If you want the client to sign the message with one certificate and the
> service to sign with another certificate - then it is already supported
> under AsymmetricBinding.
>
> Or - do you want either the client or the service to sign the message with
> two different certificates ?
>
> Thanks & regards.
> -Prabath
>
> m4rkuz wrote:
>
>>
>> ___
>> Marcus Sánchez Díaz.
>> Enterprise Developer.
>> SCJP - SCWCD.
>>
>>
>> -- Forwarded message --
>> From: *m4rkuz* mailto:m4r...@gmail.com>>
>> Date: Wed, Oct 14, 2009 at 10:50 AM
>> Subject: +Rampart Sign with two Certificates
>> To: axis-user@ws.apache.org 
>>
>>
>>
>> Hello Everyone,
>>
>> I've been using axis2+rampart for a while now, I have an application that
>> uses Axis2+Rampart for signing a validate the messages, it does this using
>> only one .JKS with a key, the same .JKS, but now I been requested to change
>> this behavior and make the app Sign the messages with one certificate and
>> then validate the response with another certificate...
>>
>> How can I accomplish this?
>>
>> This is my current policy.xml :
>>
>>
>>
>> 
>> > xmlns:wsu="
>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
>> "
>> xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
>> 
>> 
>> > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>> 
>> 
>> 
>> > sp:IncludeToken="
>> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";
>> />
>> 
>> 
>> > sp:IncludeToken="
>> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
>> ">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > sp:IncludeToken="
>> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient
>> ">
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> > xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>> 
>> 
>> http://ws.apache.org/rampart/policy";>
>> sam
>> dave
>> co.como.security.axis2.PWCBHandler
>> 
>> 
>> 
>> >
>> name="org.apache.ws.security.crypto.merlin.keystore.type">JKS
>> 
>> tomcatdir/webapps/qxIntegradorRunt/WebContent/keystore/keystore.jks
>> 
>> >
>> name="org.apache.ws.security.crypto.merlin.keystore.password">mytestkeystore
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>>
>> Any input, will be appreciated.
>>
>> Thanks
>>
>>
>> ___
>> Marcus Sánchez Díaz.
>> Enterprise Developer.
>> SCJP - SCWCD.
>>
>>
>


Re: +Rampart Sign with two Certificates

2009-10-14 Thread Prabath Siriwardena

Hi Marcus;

The 'subject' of the mail doesn't seem to reflect the same in the 
'description' of the mail - if I understood correctly...


If you want the client to sign the message with one certificate and the 
service to sign with another certificate - then it is already supported 
under AsymmetricBinding.


Or - do you want either the client or the service to sign the message 
with two different certificates ?


Thanks & regards.
-Prabath

m4rkuz wrote:


___
Marcus Sánchez Díaz.
Enterprise Developer.
SCJP - SCWCD.


-- Forwarded message --
From: *m4rkuz* mailto:m4r...@gmail.com>>
Date: Wed, Oct 14, 2009 at 10:50 AM
Subject: +Rampart Sign with two Certificates
To: axis-user@ws.apache.org 



Hello Everyone,

I've been using axis2+rampart for a while now, I have an application 
that uses Axis2+Rampart for signing a validate the messages, it does 
this using only one .JKS with a key, the same .JKS, but now I been 
requested to change this behavior and make the app Sign the messages 
with one certificate and then validate the response with another 
certificate...


How can I accomplish this?

This is my current policy.xml :




http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>


http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>



sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient"; 
/>



http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>








http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>



















http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>


http://ws.apache.org/rampart/policy";>
sam
dave
co.como.security.axis2.PWCBHandler



JKS
 
tomcatdir/webapps/qxIntegradorRunt/WebContent/keystore/keystore.jks


mytestkeystore









Any input, will be appreciated.

Thanks


___
Marcus Sánchez Díaz.
Enterprise Developer.
SCJP - SCWCD.