From dev-return-18373-archive-asf-public=cust-asf.ponee.io@ws.apache.org Tue Jul 3 19:46:52 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 02C21180632 for ; Tue, 3 Jul 2018 19:46:51 +0200 (CEST) Received: (qmail 76460 invoked by uid 500); 3 Jul 2018 17:46:50 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 76449 invoked by uid 99); 3 Jul 2018 17:46:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2018 17:46:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B791A185CCE for ; Tue, 3 Jul 2018 17:46:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.101 X-Spam-Level: X-Spam-Status: No, score=-0.101 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KAM_SHORT=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=mchsi.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 3iNWlFPBAWbZ for ; Tue, 3 Jul 2018 17:46:47 +0000 (UTC) Received: from mediacombb.net (omta010.uswest2.a.cloudfilter.net [35.164.127.233]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 743895F4A2 for ; Tue, 3 Jul 2018 17:46:46 +0000 (UTC) Received: from mediacombb.net ([68.66.77.72]) by Mediacom with SMTP id aP1YfN1TyxOQTaPNufn27O; Tue, 03 Jul 2018 17:46:39 +0000 Received: from njtozmbv26.mcomdc.com ([10.0.20.26]) by Mediacom with SMTP id aPNufB2Pd192KaPNufvzTf; Tue, 03 Jul 2018 13:46:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mchsi.com; s=20160725; t=1530639998; bh=REQKUvulOswzm6vwAKR9t6bkH3u4J/2kINPBs5TT4S8=; h=Feedback-ID:Date:From:To:Subject; b=h8Sa9B70KjtcQODWn9gRUTjQbwK1TgdVCY7U4gxfoS0JTCPLd2EiI0dtdGIUQVAyC /5RlQkuLFhdpWCtrPhEHQlo5AdtdTCUw+fwsBarXOLaN/2w/XzHvzX4Apukm1bKaa9 4F/vFXwS6pbGkEdm6KA/OPDISLXZ6YRHhdv94UI10lEoAyw5yk9qvyEKeYpuQvH85q 0qerScUCmyFi9ERrjghx2mQ0mi+Dy+0fscoVUNUyYMZ9Zr/dXLG6Od/9HQj7a0kqYT PFp0d1zmiHCam3d9RntFqMbyWdWIaT5ZdvEhe3HhLlfLp/viAvt56PnKQzvDS7QhJt gX5KrXYQsXl/Q== Feedback-ID: web::Mediacom X-Mediacom-Type: web X-Authority-Analysis: v=2.2 cv=a9xAzQaF c=1 sm=1 tr=0 a=+47Mc+Rjd7LuP37p3AAzgQ==:117 a=FKkrIqjQGGEA:10 a=Vcq7O34GSfQA:10 a=IkcTkHD0fZMA:10 a=yNNJj3OyKt8A:10 a=SSmOFEACAAAA:8 a=JYm_vhMidGpjefUAwa4A:9 a=QEXdDO2ut3YA:10 Date: Tue, 3 Jul 2018 13:46:38 -0400 (EDT) From: Jason Hall To: dev@ws.apache.org Message-ID: <2104285896.80923798.1530639998538.JavaMail.zimbra@mchsi.com> In-Reply-To: <737829073.80922833.1530639882039.JavaMail.zimbra@mchsi.com> Subject: inclusive namespace question MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [65.127.223.130] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF61 (Win)/8.0.7_GA_6021) Thread-Topic: inclusive namespace question Thread-Index: 2RcOLJqhrL3W+0mHeNNB6ASfsPuXSw== X-CMAE-Envelope: MS4wfFKP1lr1ogKE3MVh+wUc1HHx6KcGdi+vssSO7ih3NfEbKYv9F+novNEajdGu3EEv+R0/+MXr6Bl0g3KsT57FkMMUJmg61X40Oka2nEaZVsUfd3UJnUY7 Mela0fudLvpcBw+rRCEWAZrIIpJU/kGXQq5fplryUfAcpxPYKnXBritW Trying to figure out "InclusiveNamespaces" difference in SOAPUI and WSS4J implementation. In the following code snippet: Document doc = toSOAPPart(requestSoapString); //SOAPConstants soapConstants = WSSecurityUtil.getSOAPConstants(doc.getDocumentElement()); WSSecHeader secHeader = new WSSecHeader(doc); secHeader.insertSecurityHeader(); secHeader.setMustUnderstand(true); WSSecTimestamp timestamp = new WSSecTimestamp(); timestamp.setTimeToLive(300); timestamp.build(doc, secHeader); //Prepare for signature WSSecSignature builder = new WSSecSignature(); builder.setKeyIdentifierType(WSConstants.BST_DIRECT_REFERENCE); builder.setSignatureAlgorithm(WSConstants.RSA_SHA1); builder.setSigCanonicalization(WSConstants.C14N_EXCL_OMIT_COMMENTS); builder.setDigestAlgo(WSConstants.SHA1); builder.setAddInclusivePrefixes(true); builder.setUserInfo(keyAlias, keyPass); builder.setUseSingleCertificate(true); WSEncryptionPart encP = new WSEncryptionPart(WSConstants.ELEM_BODY, WSConstants.URI_SOAP11_ENV, "Content"); builder.getParts().add(encP); Document signedDoc = builder.build(doc, passwordCrypto, secHeader); String outputString = XMLUtils.PrettyDocumentToString(signedDoc); The above produces the following snippet: PEvtq8JdLh8GBzKs0Dow+DWES+k= In SOAPUI, I have chosen the same (or what I think is the same) parameters in the signature screen options . It produces the following snippet: lQsfZK8weX2vRvHYDZTl9ECLzWQ= My question is: in WSS4J - what is needed to produce the ec: ? I am sure this is something easy that I am missing ? thanks, Jason --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org For additional commands, e-mail: dev-help@ws.apache.org