Return-Path: Delivered-To: apmail-ws-wss4j-dev-archive@www.apache.org Received: (qmail 80885 invoked from network); 5 Jun 2009 18:49:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Jun 2009 18:49:49 -0000 Received: (qmail 87694 invoked by uid 500); 5 Jun 2009 18:50:01 -0000 Delivered-To: apmail-ws-wss4j-dev-archive@ws.apache.org Received: (qmail 87592 invoked by uid 500); 5 Jun 2009 18:50:01 -0000 Mailing-List: contact wss4j-dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list wss4j-dev@ws.apache.org Received: (qmail 87583 invoked by uid 99); 5 Jun 2009 18:50:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jun 2009 18:50:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cleber.t.moura@gmail.com designates 74.125.92.147 as permitted sender) Received: from [74.125.92.147] (HELO qw-out-1920.google.com) (74.125.92.147) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Jun 2009 18:49:53 +0000 Received: by qw-out-1920.google.com with SMTP id 14so1179430qwa.28 for ; Fri, 05 Jun 2009 11:49:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=FdENlNHTnL9h9uGFqt4/aja0Tp7aBAS4yDTRbKjQIAk=; b=YjresGgeUX60aFAPkLYGGoDBNkJAiaYPIrjy9ND+E2Fh/s7/fa3OP98v7oK6Y7d7ci 0DAXgD0ZnIWxhMIADmZ3rECs5QJcrHqusCUvV/D+xlmpla7DdM8pcV0rnSYEukBp9rJG lRB1FIJY4L32kgrqv8dCb3dOZUaut67QD3PHg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hyQJjkV6R12OkVvJAk/RJCB3DejIITQ9LpmzLyO7upslilfaLALU6gJJrK9ql5e3y/ zq+Vm9mjEyaWI51bkoDXCRrIDBzJVu2cXxR1O8vWCdY2da8/dfQVc674oHjDD7TGtzEg 5YGNf6ibaRXWGyjMVzmm+etvbRJ6BxrvIdUiI= MIME-Version: 1.0 Received: by 10.231.38.76 with SMTP id a12mr992507ibe.50.1244227772029; Fri, 05 Jun 2009 11:49:32 -0700 (PDT) Date: Fri, 5 Jun 2009 15:49:31 -0300 Message-ID: Subject: How to configure WSS4JOutInterceptor encryptation for multiple clients From: Cleber Moura To: wss4j-dev@ws.apache.org Content-Type: multipart/alternative; boundary=0003255749ca5f1b6a046b9e5afe X-Virus-Checked: Checked by ClamAV on apache.org --0003255749ca5f1b6a046b9e5afe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, I have the fallowing scenario: Server Side: A webservice deployed on JBoss with CXF Stack for webservices. Using ws-security for signing and encryptation of IN and OUT messages with X509 certificates. Cliente Side: Multiple clients also using ws-security for signing and encryptation of IN and OUT messages. The question is: How can the server encrypt the OUT message with the same certificate of the IN message? The samples I've found only have the 1-to-1 scenario (one server to one client). Thanks! Cleber. --0003255749ca5f1b6a046b9e5afe Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

I have the fallowing scenario:

Server Side:
A webservice deployed on JBoss with CXF Stack for webservices. Using ws-security for signing and encryptation of IN and OUT messages with X509 certificates.

Cliente Side:
Multiple clients also using ws-security for signing and encryptation of IN and OUT messages.

The question is: How can the server encrypt the OUT message with the same certificate of the IN message? The samples I've found only have the 1-to-1 scenario (one server to one client).

Thanks!

Cleber. --0003255749ca5f1b6a046b9e5afe--