IETF Logo Mail Archive

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

"Salz, Rich" <rsalz@akamai.com> Sun, 18 August 2019 21:29 UTC

Return-Path: <rsalz@akamai.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 28E071200B9 for <oauth@ietfa.amsl.com>; Sun, 18 Aug 2019 14:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 WbHmMBw2In7P for <oauth@ietfa.amsl.com>; Sun, 18 Aug 2019 14:29:25 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 BD307120047 for <oauth@ietf.org>; Sun, 18 Aug 2019 14:29:25 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x7ILRLkZ019917; Sun, 18 Aug 2019 22:29:24 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=aVcgcZspjKw3rGQDNAN2n6eeiYySFNtD9Zyi1CetSuM=; b=motMMD5CR066aN9l7W3WhlXECYEvwc0ndM+/NX8jPax+vbZ6uSlSwF9T1fF38KLQk+/V p8YQ90U2MXQkpWA3cUFYgNYosnThqt7sPxzj0uHsvbPhshHFKeyoDF93KVvRTWppE8eO r4ZQvbAwdkXSVOp0Qg9c8tmM2wLRvCkH7e8Vr9PVWhpjAlMMLqfA4pJZouIRg8+S2vhK IURGo5sL1f0bAeuHUDYu66I3aLU98ivUw7az2ZTdAvvAYLmTFgZSpL4Q3pBLjSGJrjtj uOrChGbNnqlQl+nnzjOx8K3f2zVW/ndJdQXTNSvobntrMSoylFcsiHO7FK3lYLuugv8h KQ==
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2ue6es7067-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 18 Aug 2019 22:29:24 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x7ILHHrL003496; Sun, 18 Aug 2019 17:29:23 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint3.akamai.com with ESMTP id 2uecww3mj8-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 18 Aug 2019 17:29:23 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 18 Aug 2019 17:29:22 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1473.005; Sun, 18 Aug 2019 17:29:22 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Aaron Parecki <aaron@parecki.com>
CC: "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Info on how to implement a server
Thread-Index: AQHVVSB+mqzXXWtHJ0yU+TjhKS0hzqb/7IKAgAAA+4CAAWH9AIAAVY+A///B7ACAAERhAP//wmkA
Date: Sun, 18 Aug 2019 21:29:22 +0000
Message-ID: <DF574768-3D5A-4596-9921-B2A043C7CF9D@akamai.com>
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>
In-Reply-To: <CAGBSGjq7iLHk25DMkaFwSEdqYKrqxqetH9Ceqb0FS3gBwEF7Kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1c.0.190812
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.79]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6357E6794CE3A24D8459C1B6C540E67D@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-18_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=639 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908180235
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-18_10:2019-08-16,2019-08-18 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 impostorscore=0 clxscore=1011 priorityscore=1501 adultscore=0 malwarescore=0 spamscore=0 mlxscore=0 suspectscore=0 bulkscore=0 mlxlogscore=632 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908180236
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/uu9MS0DWLg2PzTGAA6RRq0un3UY>
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:29:27 -0000

    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.

v2.23.0 | Report a Bug | By Email