Return-Path: 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 E7A021200B5 for ; Fri, 10 Jan 2020 10:50:49 -0800 (PST) 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=unavailable 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 cNtv_RdhSkFx for ; Fri, 10 Jan 2020 10:50:48 -0800 (PST) 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 E09CC1200DB for ; Fri, 10 Jan 2020 10:50:44 -0800 (PST) Received: by mail-lj1-x22c.google.com with SMTP id a13so3144019ljm.10 for ; Fri, 10 Jan 2020 10:50:44 -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=lWi/G6RTBSfBq2zRGsMF4LcmqT2n2lqWYlbmD+Rmh1c=; b=eSBZvbwi2mz16bG6dRL05g5EWhcpzmsO2OUUHTTpeVNqrE6Wb5Vx36JU0wulxdzuFf OaUrGFu4uHVp034vBg+85/Wutz1PIQ74NTa8JQFb6iD0BbNpzb2v4Wz2A9hdOQEDCmhQ dgas5ym9j2GOatDEQa8QWHFHDjOI2AKg/36d6hkdXZyQuTMxhRw87v/+03OhoRrSE4qD q9+FeQTQEv94jk0Cg1S+TrC9+XzxkRTO77KCoHZ6go5YH4M5DNs44KD9rsPAJ3hi9I5S aUlFUQiUbx69sMcKTZU1GfGeiDeWeo9McCRDjCh4XFQTscMofxa2YyXtTJLs3ePygKmZ 45Rw== 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=lWi/G6RTBSfBq2zRGsMF4LcmqT2n2lqWYlbmD+Rmh1c=; b=TzzDse2nR+StvrBN5L47OlqiobgkDzuKpLeb7XisQYwaPuyr0BXfsM05qdhcGLAVtT IPQsuekXz/9MrzKKfVxdDA22XS3JlE2058pLUt7f000d8Cic1KaI/Oejb0wdFrd/fyN4 aLG9G+lfpqJvf5NBFbvmkhpYBvZ6dLy09MbQhnku41eaHnBPqRbXUMhV9War4fJ6CJ4F Dv/2NtBwNYUCCdpIgY50WX4ObDpHc9wMzGeTM6d6FrxsSM8NCJ2hwQmtMwOq3e272tL6 VAi6yBvU8De1uYs9FCTyAkC9hRSaHMPDEC87/skIVzCxX1K/OQjUamAZvkBH/7CBrPMg 971w== X-Gm-Message-State: APjAAAWzjXw8Y3vSjWfbJrX3efWA0leZnyM6HKQDrhphzrUW5mbfnZ01 X5NoLaA0GDYQbiKR31a6mHY7uIEfPotr/IHKY6s= X-Google-Smtp-Source: APXvYqzTSywz6ReYV9WmvWYzb+plApMWUFdEAAuD0WRymm5MJdQyuOEQy3JqmRjB9cDLPmIIgyVb4iVP7zty6HxwOAo= X-Received: by 2002:a2e:7505:: with SMTP id q5mr3527092ljc.7.1578682242494; Fri, 10 Jan 2020 10:50:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Dick Hardt Date: Fri, 10 Jan 2020 10:50:31 -0800 Message-ID: To: Neil Madden Cc: Justin Richer , oauth , Mike Jones , "Richard Backman, Annabelle" Content-Type: multipart/alternative; boundary="00000000000046f793059bcd9afd" Archived-At: Subject: Re: [OAUTH-WG] [UNVERIFIED SENDER] RE: Cryptographic hygiene and the limits of jwks_uri X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jan 2020 18:50:50 -0000 --00000000000046f793059bcd9afd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable There are many other factors to resiliency than multiple instances. On Fri, Jan 10, 2020 at 10:30 AM Neil Madden wrote: > > > > On 10 Jan 2020, at 17:22, Dick Hardt wrote: > [...] > > > > =EF=BB=BFAs to the suggestion of using a JWT-decryption-microservice, a= nother > goal would be increased resiliency of the components. If the > JWT-decryption-microservice is unavailable, the whole system is > unavailable. If there are separate keys, then a failure in one component > does not fail the entire system. > > Well you can run more than one instance - it=E2=80=99s a completely state= less > service. You can also run a separate instance (or set of instances) per k= ey > if you like. > > Neil --00000000000046f793059bcd9afd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
There are many other factors to resiliency than multiple i= nstances.=C2=A0

On Fri, Jan 10, 2020 at 10:30 AM Neil Madden <neil.madden@forgerock.com> wrote:=


> On 10 Jan 2020, at 17:22, Dick Hardt <dick.hardt@gmail.com> wrote:
[...]
>
> =EF=BB=BFAs to the suggestion of using a JWT-decryption-microservice, = another goal would be increased resiliency of the components. If the JWT-de= cryption-microservice is unavailable, the whole system is unavailable. If t= here are separate keys, then a failure in one component does not fail the e= ntire system.

Well you can run more than one instance - it=E2=80=99s a completely statele= ss service. You can also run a separate instance (or set of instances) per = key if you like.

Neil
--00000000000046f793059bcd9afd--