Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FA6ABFC4 for ; Wed, 4 Jan 2012 09:42:13 +0000 (UTC) Received: (qmail 44234 invoked by uid 500); 4 Jan 2012 09:42:13 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 43879 invoked by uid 500); 4 Jan 2012 09:41:56 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 43861 invoked by uid 99); 4 Jan 2012 09:41:53 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 09:41:53 +0000 Received: from localhost (HELO mail-qw0-f41.google.com) (127.0.0.1) (smtp-auth username coheigea, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 09:41:52 +0000 Received: by qabg40 with SMTP id g40so9259667qab.0 for ; Wed, 04 Jan 2012 01:41:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.10.19 with SMTP id n19mr64993773qan.68.1325670111827; Wed, 04 Jan 2012 01:41:51 -0800 (PST) Reply-To: coheigea@apache.org Received: by 10.224.197.138 with HTTP; Wed, 4 Jan 2012 01:41:51 -0800 (PST) In-Reply-To: <1325631779008-5118234.post@n5.nabble.com> References: <1321378614937-4995094.post@n5.nabble.com> <1321467209797-4998600.post@n5.nabble.com> <1321553229128-5001988.post@n5.nabble.com> <1322529527685-5030781.post@n5.nabble.com> <1416917.YXJ4fJfth3@dilbert.dankulp.com> <1325610039284-5117386.post@n5.nabble.com> <1325625435645-5117995.post@n5.nabble.com> <1325631779008-5118234.post@n5.nabble.com> Date: Wed, 4 Jan 2012 09:41:51 +0000 Message-ID: Subject: Re: General security error (Provided SAML token does not contain a suitable key) From: Colm O hEigeartaigh To: dev@cxf.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What does the WSDL of the service look like? Does it have a SecureConversationToken policy? Colm. On Tue, Jan 3, 2012 at 11:02 PM, danlee100 wrote: > Here is the actual SOAP message > > > POST http://66.211.102.200/gen4/services/AssessmentDataService HTTP/1.1 > Content-Type: application/soap+xml; charset=3Dutf-8 > Host: 66.211.102.200 > Content-Length: 1267 > Expect: 100-continue > Accept-Encoding: gzip, deflate > Connection: Keep-Alive > > xmlns:a=3D"http://www.w3.org/2005/08/addressing"> s:mustUnderstand=3D"1">http://docs.oasis-open.org/ws-sx/ws-trust/200512/R= ST/Issueurn:uuid:ce0cca36-02d5-4fbc-873e-5756a5f676= 47http://www.w3.org/2005/08/addressing/= anonymous s:mustUnderstand=3D"1">http://66.211.102.200/gen4/services/AssessmentData= Service Context=3D"uuid-f7972e39-96c7-4621-bc43-c5ba53c68655-1" > xmlns:trust=3D"http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/sct<= /trust:TokenType>http://docs.oasis-open.org/ws-sx/ws-tru= st/200512/Issue256 ValueType=3D"http://schemas.xmlsoap.org/ws/2005/02/trust/tlsnego" > EncodingType=3D"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-s= oap-message-security-1.0#Base64Binary">FgMBAFwBAABYAwFPA4We+Mq1fvk/zjwX4jic= rc+V7cdBjHStS8Lr0xAsYwAAGAAvADUABQAKwAnACsATwBQAMgA4ABMABAEAABcACgAIAAYAFwA= YABkACwACAQD/AQABAA=3D=3D > > > -- > View this message in context: http://cxf.547215.n5.nabble.com/Re-General-= security-error-Provided-SAML-token-does-not-contain-a-suitable-key-tp499048= 9p5118234.html > Sent from the cxf-dev mailing list archive at Nabble.com. --=20 Colm O hEigeartaigh Talend Community Coder http://coders.talend.com