Re: [OAUTH-WG] Info on how to implement a server
John Bradley <ve7jtb@ve7jtb.com> Sat, 17 August 2019 18:30 UTC
Return-Path: <ve7jtb@ve7jtb.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 A839C12006D for <oauth@ietfa.amsl.com>; Sat, 17 Aug 2019 11:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=ve7jtb-com.20150623.gappssmtp.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 zvgamqBlbDsw for <oauth@ietfa.amsl.com>; Sat, 17 Aug 2019 11:30:38 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 5EEAF120041 for <oauth@ietf.org>; Sat, 17 Aug 2019 11:30:38 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id 125so7476925qkl.6 for <oauth@ietf.org>; Sat, 17 Aug 2019 11:30:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=f+udEwfrgYuckxhLaunIf3FH7q2tfzsDWHZRoBU1XT0=; b=0Z+FA+ODknGoG7jAWcCDtECNAxE2Uuur55NY3u45qqwRwlc12lhZ8yi67y2hV2ZyY0 PqUlDuiWWIKfkaAsElwsMyTJtqA8HBWfMqPaBbuR2ffEmQQAWoZ1bipbp8REgDeCeY7k w5klkiRqPPkIRI2OlraJtDelcpCNk6TUrj3dljuBFGbPTZUvJ8Zlp/zvcTkdQw0ryT3G 8iDKzlS7MkEK5tuwnBU8M6xBMMeOu2ywSoZP6P8SQYB3/GzEm9ErWwjKqhxyhY86lluf 7UfYqiyl7QxbQt/v1/2e+CdFwRm9vfl8Tnev4Cstqbh4qm0k4A/o1+R7fYDGqg/7QLNC AV/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=f+udEwfrgYuckxhLaunIf3FH7q2tfzsDWHZRoBU1XT0=; b=M3qytzdGD6dEniXuEbopXzr3LqT+vUdtbc+m8jerqFLcYqbOJVPSAVlbfbDUXnDBZA wCHACjJk8SJebv2XDF/phOcWGc1XI5Sk/pARPtTtMz565TQhNQYU4qOQtPPVVORyDqS/ MUI1UiEGd6WoLxe15ekj+VAg/GdmHo6uImk1TZXGo4K1NLfVvx7lJ+PejmFYQHgfEBgg rNKdSmVDJfEJ+4YLBmzjPLIuK5KY0VaPFuuGEI+1JXnNbPN9LNnX7pw1d/qiTDeSnLEs hLRtq/L/Qrf6PiHb5CC3roHrvyfRzJxPpSz1+M4zAqK+sSlUHHkCSjbMs6EkaazQ8H18 N0XQ==
X-Gm-Message-State: APjAAAVtzFsp/3sLMsyxMITM/wUBwuIGpWZoTPafBNrhyG+28kyF4sdI h9mkbO/q3lOAl3Fcxg3c2sHd/dSGh/zy70+5
X-Google-Smtp-Source: APXvYqxEqpasMTaK/zrtWg7deVgSALvECZKV9OpiOSCyTq/298VBe7KkrJ1bvMjSys2q2iLWk27Tmw==
X-Received: by 2002:a37:6248:: with SMTP id w69mr14248978qkb.225.1566066636679; Sat, 17 Aug 2019 11:30:36 -0700 (PDT)
Received: from [192.168.8.103] ([181.203.52.123]) by smtp.gmail.com with ESMTPSA id t124sm4741926qke.31.2019.08.17.11.30.34 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Aug 2019 11:30:35 -0700 (PDT)
To: oauth@ietf.org
References: <D3FB5975-2448-445B-8B48-0A46D43E0A99@akamai.com>
From: John Bradley <ve7jtb@ve7jtb.com>
Message-ID: <bc37895b-b4c9-af54-dbfc-6aa2cd80b75b@ve7jtb.com>
Date: Sat, 17 Aug 2019 14:30:33 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <D3FB5975-2448-445B-8B48-0A46D43E0A99@akamai.com>
Content-Type: multipart/alternative; boundary="------------2A3F2B903D4D83B50B86A37C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/W7ZybDhlpzREyOAAdf0KU1HxftA>
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: Sat, 17 Aug 2019 18:30:41 -0000
The openID Connect kind of OAuth server. OAuth on its own is not designed to be secure for identity federation. John B. On 8/17/2019 1:23 PM, Salz, Rich wrote: > > What’s the WG consensus (heh) on the best guide to adding OAUTH > support to an existing server so that it can act as an identity > provider? Which version of oauth is most widely deployed by relying > parties these days? > > > > I want to add OAUTH support to the IETF datatracker. > > > > Thanks for any pointers. Replies to me will be summarized for the list. > > > > /r$ > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Info on how to implement a server Salz, Rich
- Re: [OAUTH-WG] Info on how to implement a server John Bradley
- Re: [OAUTH-WG] Info on how to implement a server Hans Zandbelt
- Re: [OAUTH-WG] Info on how to implement a server Salz, Rich
- Re: [OAUTH-WG] Info on how to implement a server Dick Hardt
- Re: [OAUTH-WG] Info on how to implement a server Salz, Rich
- Re: [OAUTH-WG] Info on how to implement a server Dick Hardt
- Re: [OAUTH-WG] Info on how to implement a server Aaron Parecki
- Re: [OAUTH-WG] Info on how to implement a server Salz, Rich
- Re: [OAUTH-WG] Info on how to implement a server Salz, Rich
- Re: [OAUTH-WG] Info on how to implement a server Dick Hardt
- Re: [OAUTH-WG] Info on how to implement a server Salz, Rich