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 3572B933D for ; Tue, 3 Jan 2012 17:01:07 +0000 (UTC) Received: (qmail 55260 invoked by uid 500); 3 Jan 2012 17:01:06 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 55147 invoked by uid 500); 3 Jan 2012 17:01:05 -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 55139 invoked by uid 99); 3 Jan 2012 17:01:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 17:01:05 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=FORGED_YAHOO_RCVD,FREEMAIL_ENVFROM_END_DIGIT,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 17:01:00 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Ri7j5-0007Mm-9O for dev@cxf.apache.org; Tue, 03 Jan 2012 09:00:39 -0800 Date: Tue, 3 Jan 2012 09:00:39 -0800 (PST) From: danlee100 To: dev@cxf.apache.org Message-ID: <1325610039284-5117386.post@n5.nabble.com> In-Reply-To: <1416917.YXJ4fJfth3@dilbert.dankulp.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> Subject: Re: General security error (Provided SAML token does not contain a suitable key) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I just noticed that CXF 2.5.1 is out now. Is the problem I supported fixed in this release? Let me know if you know offhand. I guess I could download it and test it, but I would like to know if you could tell me. Thanks. -- View this message in context: http://cxf.547215.n5.nabble.com/Re-General-security-error-Provided-SAML-token-does-not-contain-a-suitable-key-tp4990489p5117386.html Sent from the cxf-dev mailing list archive at Nabble.com.