IETF Logo Mail Archive

Re: codimd.ietf.org now uses auth.ietf.org as its identity provider

Robert Sparks <rjsparks@nostrum.com> Fri, 21 August 2020 13:33 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789613A0528 for <wgchairs@ietfa.amsl.com>; Fri, 21 Aug 2020 06:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.028
X-Spam-Level:
X-Spam-Status: No, score=-3.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.949, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 EAMygRPn2cRR for <wgchairs@ietfa.amsl.com>; Fri, 21 Aug 2020 06:33:55 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 5983B3A043E for <wgchairs@ietf.org>; Fri, 21 Aug 2020 06:33:55 -0700 (PDT)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 07LDXnxf012946 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 21 Aug 2020 08:33:50 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1598016833; bh=MTIx2sHFctIpvo7Y5dt9m5BIg9Qa09U0ehhBjGL2LqY=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=FamGLsFEP4ptcwqe7tFtf4/Vo8iIeurjpKBaNKKXIektJt+gXc0MOCq+GlUd9MKom +1dctd0kPf2tCaItgL73wlYvedmhV0XOjRQWTB6TVcsCw7fPVg+fySAw/rdJVf2EVt rR84DWTLTkhRqekfuFG9MPNXGuRL0rnOUKRVpR3M=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
Subject: Re: codimd.ietf.org now uses auth.ietf.org as its identity provider
To: Russ Housley <housley@vigilsec.com>, Carsten Bormann <cabo@tzi.org>
Cc: IETF WG Chairs <wgchairs@ietf.org>
References: <8513b5f5-33f4-b22d-bf40-f805058f3104@nostrum.com> <0BB902E6-B635-450F-A5A0-EEAECF742002@tzi.org> <370E8A40-A8E9-483C-B3C0-757977CA34C5@vigilsec.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <30470f7c-8c4a-c965-be3d-278f301475cb@nostrum.com>
Date: Fri, 21 Aug 2020 08:33:49 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <370E8A40-A8E9-483C-B3C0-757977CA34C5@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/GDDaJCy_9oZPFGvKVmrZgoyECFQ>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2020 13:33:56 -0000

On 8/21/20 8:02 AM, Russ Housley wrote:
>
>> On Aug 21, 2020, at 8:48 AM, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> On 2020-08-20, at 19:04, Robert Sparks <rjsparks@nostrum.com> wrote:
>>> the first time you login again (consequently using auth.ietf.org) you will have to
>> … wait a LOONG time, don’t give up prematurely, it does work.
> I tried it yesterday, and it took s long time too.  However, today it is very quick.  I cannot think of any caching in the browser that would account for the difference.
It's not caching in the browser - it's whether the apache worker that 
you attached to has to initialize (load the backing python libraries or 
not). We are tuning so that the long wait goes away.
>
> Russ
>
>

v2.23.0 | Report a Bug | By Email