Re: [OAUTH-WG] Info on how to implement a server

Dick Hardt <dick.hardt@gmail.com> Sun, 18 August 2019 21:31 UTC

Return-Path: <dick.hardt@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 00E771200B9 for <oauth@ietfa.amsl.com>; Sun, 18 Aug 2019 14:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qq0h4Ia4lsFL for <oauth@ietfa.amsl.com>; Sun, 18 Aug 2019 14:30:59 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 9DD91120047 for <oauth@ietf.org>; Sun, 18 Aug 2019 14:30:58 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id z17so9731727ljz.0 for <oauth@ietf.org>; Sun, 18 Aug 2019 14:30:58 -0700 (PDT)
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=LmAWXZ7c96mOEgU1YDesBuN0sSJOUMNO//OJOQe18xs=; b=sLyRogtxtCbz8CluTdufhNhUWqlOmMTZFu7wdg2XNNAluJVTmS2t2oMfQFxfa5adJA plxyggOLlOdiJfJJbm1wm7ITKaGDqIxWcOUM2gPRyA80fLUoG9vPVF8VjznbbNue0tvf 1yEmhDFQ+2sIC260ZPvyd80P8LV2CKDPyinD4l6Zjch9onKL8KTrlEoWQcDuu/CvL0AE ilx+kwgp4bUd8ZUgYuxdtF7xgl/PsrYCgfZp0liUpsN2H8uivDd2mOF/F1Gu2Pz6VrwK YOwDBfsq4zEjpfi0vRcMe41+LoePwtYaB90QIPH2wZwX0vwYTgZ9xH6Vk+/TF8edPSOh QutA==
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=LmAWXZ7c96mOEgU1YDesBuN0sSJOUMNO//OJOQe18xs=; b=H7bK4O8xRAUMZv0EPJvM4PXK6QLcIUBMyMNBs/8KeMA1Dvm+mkIzHy/oWG0e0BCMFU YvTlkg202PJK452YPBVaHXATPaoTOQD0YpUndCH/VmC1oYruB3zzKnsI4h6LQc11GYiD IvmElOkuK9qKzNs+y8G50Myh8ttg79Vkpw/w/cpAGaROfos2t3sKaIsJMVi+fWo++lOu T/aTMIOw07jq/K8Qvvv4nGyCSRe0ASo7Qis6mEj19KJJMItknWGI3CGgt9cqMdXUWJD1 gPO0/sebUsIW8NQqtI3i2Ll2vE5Xx8dkwDtSpar5VqmXfHWvRJEXQH+BiLidXa3hSEL6 5iDw==
X-Gm-Message-State: APjAAAW0YNuE4TMFuWToUH2hl8EsI8BkrCZpvj+jgxZe22ElmdmNGJmS mRzCZ3DP7P24ZBLPAYHCvbUqXJ41i/DnM9Ew07c=
X-Google-Smtp-Source: APXvYqy0D+PuMZWDmOehfdR66mYvhysQccBuXwrCy5g8pQIJWpG2TnUsOfV7o/UspitHjav6DMKu1mQPKQgGXd5w2WU=
X-Received: by 2002:a2e:81cb:: with SMTP id s11mr10619305ljg.179.1566163856772; Sun, 18 Aug 2019 14:30:56 -0700 (PDT)
MIME-Version: 1.0
References: <D3FB5975-2448-445B-8B48-0A46D43E0A99@akamai.com> <bc37895b-b4c9-af54-dbfc-6aa2cd80b75b@ve7jtb.com> <CA+iA6uifvqv=18ZYLf+BmDYhp6ZyEvwv+9mWoL37ALWuqozj4w@mail.gmail.com> <74BEF7B5-55AC-4BD6-AEF1-D04DEFE9F0EA@akamai.com> <CAD9ie-s+03oHh+1+Y5cVhUoBs1zZs1CM_iSzmf-opnpwNbMyPA@mail.gmail.com> <40AA5F98-4EB1-4ECB-A9A6-AEB2E435F693@akamai.com> <CAGBSGjq7iLHk25DMkaFwSEdqYKrqxqetH9Ceqb0FS3gBwEF7Kw@mail.gmail.com> <DF574768-3D5A-4596-9921-B2A043C7CF9D@akamai.com>
In-Reply-To: <DF574768-3D5A-4596-9921-B2A043C7CF9D@akamai.com>
From: Dick Hardt <dick.hardt@gmail.com>
Date: Sun, 18 Aug 2019 14:30:45 -0700
Message-ID: <CAD9ie-uoEaNF3i1M0bEu348edh2hoZcnrqe8t=znu6yikmgWgw@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Aaron Parecki <aaron@parecki.com>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000057d0f305906af037"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/ZrvK1q5zvXx1mDdgJTADeDocDoY>
Subject: Re: [OAUTH-WG] Info on how to implement a server
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: Sun, 18 Aug 2019 21:31:01 -0000

On Sun, Aug 18, 2019 at 2:29 PM Salz, Rich <rsalz@akamai.com>; wrote:

>     Not to be pedantic, but adding OAuth support is a mechanism in support
>     of a goal. What's the end goal?
>
>     * Letting third party apps use the datatracker API?
>     * Letting people sign in to other apps with a datatracker account?
>

> The latter.
>

Then you want OpenID Connect



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