Return-Path: X-Original-To: apmail-incubator-amber-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-amber-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EDC05D91F for ; Thu, 18 Oct 2012 12:35:14 +0000 (UTC) Received: (qmail 20826 invoked by uid 500); 18 Oct 2012 12:35:14 -0000 Delivered-To: apmail-incubator-amber-dev-archive@incubator.apache.org Received: (qmail 20596 invoked by uid 500); 18 Oct 2012 12:35:12 -0000 Mailing-List: contact amber-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: amber-dev@incubator.apache.org Delivered-To: mailing list amber-dev@incubator.apache.org Received: (qmail 20540 invoked by uid 99); 18 Oct 2012 12:35:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2012 12:35:10 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.214.47] (HELO mail-bk0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2012 12:35:01 +0000 Received: by mail-bk0-f47.google.com with SMTP id jk7so3684816bkc.6 for ; Thu, 18 Oct 2012 05:34:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version:x-mailer:x-gm-message-state; bh=nxt68xWY89IyfZSyaPsbS37wWQXB3B0MNiFTSGBfh50=; b=R1AYOjTk9UcdS12IFuCGR1n5+I28VkEX6a3B9IRfQZ8ytNyTU39+1btOV/YPsa+uro 1g4pRZmXpoBll4IvMfiD83HFNPkmaK2SAgSpDN2D3J+7xRSBQ/artgeC0R2Cs3rJgVDm BWPMIxsXqO1YPZCwHtFBSKUFwDTzFQZOLVW/5WS1H6dNGpB/z+ZtKWgyCQYJCnayRMfH HL/PixkDAFp4fX0uA9yvHTU+re7ivN5LW5VquW/Tm6kXb+POXE/XyTTHSyaGbkqPU8RY n2iWpq5M/oEBx34SyFO0AEJj1918HzZEA2chbfjamwaV/E614GA+gXnAVjCAI3vHE64r ppYw== Received: by 10.204.156.18 with SMTP id u18mr6250879bkw.131.1350563680214; Thu, 18 Oct 2012 05:34:40 -0700 (PDT) Received: from [192.168.2.21] (ipd50a9e19.speed.planet.nl. [213.10.158.25]) by mx.google.com with ESMTPS id v14sm14792525bkv.10.2012.10.18.05.34.39 (version=SSLv3 cipher=OTHER); Thu, 18 Oct 2012 05:34:39 -0700 (PDT) From: Stein Welberg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Handling and creating OAuth error messages Message-Id: <68982ACD-BE38-456C-A75D-CB222CCF4A81@innovation-district.com> Date: Thu, 18 Oct 2012 14:34:38 +0200 To: amber-dev@incubator.apache.org Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\)) X-Mailer: Apple Mail (2.1498) X-Gm-Message-State: ALoCoQnRb/GA+n7KYkyQVT9+B2WVnpz8cpBAsTLcorJ6ugK1jmuC9m91H6c7LGFhYUyxZJdqX7jR X-Virus-Checked: Checked by ClamAV on apache.org Hi Guys, I recently started working with the Amber Authorization server = implementation. I also have looked at other implementations but Amber = gives me the most flexibility in adding an OAuth authorization server to = our Saas platform. However, the current amber implementation gives me some challenges. I = run into the following when it comes to handling OAuth errors. Amber = gives me some handles but it requires me to have a quite extensive = understanding of the OAuth spec in order to get spec compliant messages. = Basically Amber gives me not much help in handling OAuth compliant error = messages. Are you planning on improving this or is it intentionally done the way = it is done? Regards, Stein Welberg