Re: [OAUTH-WG] The response from the Google authorization endpoint

Alex Kalp <alexkalps@gmail.com> Thu, 05 November 2020 13:47 UTC

Return-Path: <alexkalps@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC18B3A114D for <oauth@ietfa.amsl.com>; Thu, 5 Nov 2020 05:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2AwjjSKy819Z for <oauth@ietfa.amsl.com>; Thu, 5 Nov 2020 05:47:07 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDBA63A1136 for <oauth@ietf.org>; Thu, 5 Nov 2020 05:47:06 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id y12so1834092wrp.6 for <oauth@ietf.org>; Thu, 05 Nov 2020 05:47:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AnY+kWzP77FnFP4YETbg3LaivzfNM76XuLQ+vzTfpg8=; b=C/VkP/RkCkVri2V3VPJRNFvRslWbzf/DudQ7e1zemnqEwAiW2uZa87NSkVLkRCGa5G 9Byxj660FV38M258O4fwSE2gncO6pNnb4CQ03AgOphec0om3OL46cdLHwnTE+omJky95 eXQudBE/rMCr/kg9qKIK0DbwOVBrY5FOQ80ycjf5RgV3OMOx/d1JGNzmXzdzeDGOFPSx IzIZmiGuGSIVMqglVAiCHR86faiEAJPla6Sdlvyofyocd373TPWfu6OP+NrTUCbHLX7i 7fjlpJaghchiSKy/8p6s6Y6I5zPLD2tBdLNzO+LvVtDdWCZIkgHaEJqTodaW0VzaUVSR YWdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AnY+kWzP77FnFP4YETbg3LaivzfNM76XuLQ+vzTfpg8=; b=G5Rd+739RwzNIFZuCglscoENWAyGG5yTlzweMdDPeWrkcg0WdHuem9ImzMHdS1WtZS nMKLsH3dceAYcJjFhXVRT6+bg0oOKqqsEkhaIfCRI8GR6b4HFiod7XqfpJV+XsmyEvYj upt4XONkR4mnD7R1zYomYLUZu6rslgoIyC0zocDI0KoyYzjGvANbDBgOMVStAkU9Lf4d 2603zPt+kj/6RWG1nLnzskYhJJPAmweXFwC910gZFfg5TZ0nbNSMQnHAGNRENY5Yn+ct 4otT8NJrgRqK9Q+hFldeGyz4/KCweNBnguU9Ha1TV1mCXLJc1QKt4o6Tnpk/Ot/A1q/h O+Fg==
X-Gm-Message-State: AOAM533SCzn/4aniECujOvELnG4liqLNRqGSHSH82WgIJ6XHbA3PKP5A xdOd1yQQKEU3lHpvLJziJI5e+6ZjlprmbIAF9RRJqiMxnZSUPA==
X-Google-Smtp-Source: ABdhPJxuR3w8hh0qwKuMzr8VNqwe3OurpF1wvvw2pDfIyJkImb71PEU9E5JUAfFk/kmVdOJBcX+btxoFn/pTAwBx33c=
X-Received: by 2002:a5d:5703:: with SMTP id a3mr3108564wrv.67.1604584025301; Thu, 05 Nov 2020 05:47:05 -0800 (PST)
MIME-Version: 1.0
References: <CA+YokQ0uT3FuJE155tNtp1OHz80wPu+e39wiJNWnx_g5jZFGZA@mail.gmail.com> <188bcca0-e2d9-2f8d-89a5-cdf653849ce9@connect2id.com>
In-Reply-To: <188bcca0-e2d9-2f8d-89a5-cdf653849ce9@connect2id.com>
From: Alex Kalp <alexkalps@gmail.com>
Date: Thu, 05 Nov 2020 05:47:56 -0800
Message-ID: <CA+YokQ0GFdM431JM1SWor=zt1POw1PSLH_o7y2_99LJ1x18JFg@mail.gmail.com>
To: Vladimir Dzhuvinov <vladimir@connect2id.com>
Cc: oauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d726bc05b35c5447"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/qnwkxGxV2KD3fUi3HLGIyQcxcS0>
Subject: Re: [OAUTH-WG] The response from the Google authorization endpoint
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2020 13:47:09 -0000

Hi Vladimir,

Thanks for the reply. Would be great if you can share your insights on how
those parameters are being used.

I could not find any public docs explaining their usage, so thought they
probably are being used by the Google applications by themselves.

Thanks!


On Wed, Nov 4, 2020 at 9:00 PM Vladimir Dzhuvinov <vladimir@connect2id.com>
wrote:

> Hi Alex,
>
> OAuth 2.0 doesn't forbid other params to be present in the response. If
> you find such - ignore them.
>
> https://tools.ietf.org/html/rfc6749#section-4.1.2
>
> The client MUST ignore unrecognized response parameters.
>
> I have a theory why those 3 extra params (scope, authuser, prompt) are
> there, but I don't think it would matter in your case.
>
> Vladimir
> On 05/11/2020 02:23, Alex Kalp wrote:
>
> Hi All,
>
> While trying out the OAuth 2.0 authorization code grant type with Google,
> I got the following response to my registered redirect_uri.
>
> https://localhost:9000/app_uri?*state*=caf324471khs872&%20*code*
> =4/5wFzvDar86R-AJWCIE&%20*scope*=profile%20openid%20
> https://www.googleapis.com/auth/userinfo.profile&%20*authuser*=0&%20
> *prompt*=consent
>
> As per the RFC6749 section 4.1.2, the authorization response from the
> authorization endpoint only includes code and state.
>
> Appreciate if you can share any insights on why Google adds scope,
> authuser and prompt parameters to the response, which are not in the OAuth
> 2.0 RFC - and do we consider those additional parameters as a violation of
> the RFC6749?
>
> Thanks!
> -Alex
>
>
>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
> --
> Vladimir Dzhuvinov
>
>