Re: [OAUTH-WG] OAUTH for Web Proxy authentication

Markus <markus@moeller.plus.com> Tue, 31 January 2023 23:49 UTC

Return-Path: <markus@moeller.plus.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 7F194C153CA1 for <oauth@ietfa.amsl.com>; Tue, 31 Jan 2023 15:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.691
X-Spam-Level:
X-Spam-Status: No, score=-2.691 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=plus.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYzeFyIGgdaU for <oauth@ietfa.amsl.com>; Tue, 31 Jan 2023 15:49:37 -0800 (PST)
Received: from avasout-ptp-003.plus.net (avasout-ptp-003.plus.net [84.93.230.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0ADC1527AE for <oauth@ietf.org>; Tue, 31 Jan 2023 15:49:36 -0800 (PST)
Received: from Ultrabook1 ([81.174.172.105]) by smtp with ESMTPA id N0NVpuuFyOgYDN0NZpki2T; Tue, 31 Jan 2023 23:49:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=plus.com; s=042019; t=1675208974; bh=SWFQyw08sOyDGrhfVRBrbr7Az/Dr6vUSZpp6uEKwQeQ=; h=From:To:Cc:References:In-Reply-To:Subject:Date; b=Bqb4gg1zIAOfzJX5QJ8oXNJ6E2zDEIamoPfDSP6NAzYLdTf6v5KbbN0HM3p1MXVDQ U/TzI1OVRzkVuAwX8d+lWnQV4kmKT1dxGyHyCtKONN2fLWp7Ewtb5FiDL3XAQ6h9db celLPCxvH6uYVR/jk6QwFtSSwCSVg6MCZCV8/z+lgOW3dfpU7AzkLjw0muGBquQu6Q h0yiBtItXMifQ/E0FlOO0sYgE81BviKhfPccBnyPgt7NFQvd0P3mhZyFP8sG7MFm/s ixpvbAkWedS+Ud5nUe9nHZ9eog6TU09OVFayQNZqBk2PEpKZ8eTY90Z50rGPldlucD Y6/mA2A/thxRA==
X-Clacks-Overhead: "GNU Terry Pratchett"
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.4 cv=CZQbWZnl c=1 sm=1 tr=0 ts=63d9a90e a=Cgy7cPM/+uUNK5d9KfAcsw==:117 a=Cgy7cPM/+uUNK5d9KfAcsw==:17 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=EBOSESyhAAAA:8 a=rztzz8zuAAAA:8 a=tAp8l2iYVeW_Ma04bZAA:9 a=wPNLvfGTeEIA:10 a=ToKlFuollLkA:10 a=pGLkceISAAAA:8 a=3oc9M9_CAAAA:8 a=KnSv1_dvaHDJte60UuIA:9 a=bLwcma28J7VWDxjL:21 a=_W_S_7VecoQA:10 a=w1C3t2QeGrPiZgrLijVG:22 a=yJM6EZoI5SlJf8ks9Ge_:22 a=utNLEOu7vwYDzd2dY_SC:22
X-AUTH: moeller+markus@:2500
Message-ID: <ECAB9788D96C40D18BB6126DCEC92D6D@Ultrabook1>
From: Markus <markus@moeller.plus.com>
To: Neil Madden <neil.e.madden@gmail.com>, Warren Parad <wparad=40rhosys.ch@dmarc.ietf.org>
Cc: oauth@ietf.org
References: <5E5CAC37F6AB415CA3A8CF2D55120412@Ultrabook1> <9955924b-85d4-3165-b40a-ab53b7a5f61d@aol.com> <150CA19C7723490D8075BBF5E9F76E24@Ultrabook1> <CADNypP8Cz8s1wjMnp8W-7rPXB=n5BEqAkiUT+K6ow-w2BiQ2Aw@mail.gmail.com> <41EB1D2052534C919E82CE58DA4ED80F@Ultrabook1> <CAJot-L37ZVkV+RSdCunGemK0X+VtxKv5WXuvnBpo3hBuk-g25g@mail.gmail.com> <6C014642-8984-4AD1-9145-880FB004BD80@gmail.com>
In-Reply-To: <6C014642-8984-4AD1-9145-880FB004BD80@gmail.com>
Date: Tue, 31 Jan 2023 23:49:28 -0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D9_01D935CE.A80ADE80"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
X-CMAE-Envelope: MS4xfOkngkkSPfVnvSkXpBZrTp/EIK17+0uKRD1rZvVjTjmf2GouMDeLUQnqq49G5jxWTwx4p03RSAo1Y7UgILR940wrMuhLjKnZdU3pMB6AKL5I4A9a0r0s KwZvtamfjgJWdj6TLtNoWBtux1jYYRcqs390icn1qx2dbLHngiSFtJT1gqHa8Ws22GW7xQC/lPC8LQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/RKqcuhgISkOiBfC81GF2oi-HI34>
Subject: Re: [OAUTH-WG] OAUTH for Web Proxy authentication
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 31 Jan 2023 23:49:41 -0000

Hi Neil,

   If I understand correctly the RFC already allows the use of Bearer authentication scheme for Proxy authentication and it is more an implementation question ? 

Thank you 
Markus

From: Neil Madden 
Sent: Tuesday, January 31, 2023 10:32 AM
To: Warren Parad 
Cc: Markus ; oauth@ietf.org 
Subject: Re: [OAUTH-WG] OAUTH for Web Proxy authentication

Right - RFC 6750 doesn't explicitly define how to send an access token with the Proxy-Authorization/Proxy-Authenticate headers, but states: 

   The Bearer authentication scheme is intended primarily for
   server authentication using the WWW-Authenticate and Authorization
   HTTP headers but does not preclude its use for proxy authentication.
As far as I'm aware you can use it in a straightforward way with those headers for proxy auth, the same as for any other HTTP auth scheme (i.e., literally just rename the headers in the examples).

I think the sticking point will be how browsers respond to a Proxy-Authenticate header with scheme Bearer. I guess not very well, given that they won't know where the AS is. You'd need something like UMA's as_uri hint in the challenge and then you'd need to get browsers to implement that. 

It's not really clear what OAuth adds to this scenario anyway - there's no scope restriction going on, right? These days I guess most proxy usage is a single CONNECT and then its just a dumb tunnel for encrypted traffic - unless you're doing TLS interception, in which case I think the IETF and browser vendors won't be very interested - see e.g. RFC 7258 (Pervasive Monitoring Is an Attack).

-- Neil


  On 31 Jan 2023, at 09:47, Warren Parad <wparad=40rhosys.ch@dmarc.ietf.org> wrote:

  Markus could you shed some light on how this would be different from the normal OAuth flow between any resource server and the user agent? Proxies today could already start accepting OAuth authorization following the OAuth spec, right?

  On Tue, Jan 31, 2023 at 12:48 AM Markus <markus@moeller.plus.com> wrote:

    Hi Rifaat,

        Right now a browser uses either basic , NTLM,  Kerberos or Negotiate authentication to a proxy which are all old methods and not anymore appropriate with Microsoft AD moving to Azure AD. Other methods like OAUTH might now be more appropriate assuming enterprises still require proxy based controls at their borders to the Internet.

    Regards
    Markus

    From: Rifaat Shekh-Yusef 
    Sent: Monday, January 30, 2023 6:12 PM
    To: Markus 
    Cc: oauth@ietf.org ; George Fletcher 
    Subject: Re: [OAUTH-WG] OAUTH for Web Proxy authentication

    Hi Markus, 

    As Goerge mentioned, there is no such document that covers this.
    What use case(s) do you have in mind for this?

    Regards,
    Rifaat


    On Sat, Jan 28, 2023 at 7:50 PM Markus <markus@moeller.plus.com> wrote:

      Thank you.

      Regards
      Markus
      From: George Fletcher 
      Sent: Saturday, January 28, 2023 1:43 PM
      To: Markus; oauth@ietf.org 
      Subject: Re: [OAUTH-WG] OAUTH for Web Proxy authentication

      To my knowledge that spec doesn't exist. I'll let others chime in if they have seen a proposal in that regard.

      In regards to which working group, given the core topic is OAuth authorization, I would present it here at a minimum.

      Thanks,
      George


      On 1/22/23 7:06 AM, Markus PlusNet wrote:

        Dear WG,

            I am new to oauth and wonder which WG would be responsible for reviewing a Spec for Proxy authentication https://httpwg.org/specs/rfc9110.html#auth.client.proxy using oauth or does that spec already exist ?

        Thank you
        Markus


         
_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth


      _______________________________________________
      OAuth mailing list
      OAuth@ietf.org
      https://www.ietf.org/mailman/listinfo/oauth

    _______________________________________________
    OAuth mailing list
    OAuth@ietf.org
    https://www.ietf.org/mailman/listinfo/oauth

  _______________________________________________
  OAuth mailing list
  OAuth@ietf.org
  https://www.ietf.org/mailman/listinfo/oauth