IETF Logo Mail Archive

Re: [OAUTH-WG] SPOP - code verifier requirements

Chuck Mortimore <cmortimore@salesforce.com> Wed, 15 October 2014 15:27 UTC

Return-Path: <cmortimore@salesforce.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8AD81A87C5 for <oauth@ietfa.amsl.com>; Wed, 15 Oct 2014 08:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.578
X-Spam-Level:
X-Spam-Status: No, score=-0.578 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 q8YHF_pArUjB for <oauth@ietfa.amsl.com>; Wed, 15 Oct 2014 08:27:33 -0700 (PDT)
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA6B31A87C3 for <oauth@ietf.org>; Wed, 15 Oct 2014 08:27:33 -0700 (PDT)
Received: by mail-oi0-f43.google.com with SMTP id u20so1146737oif.16 for <oauth@ietf.org>; Wed, 15 Oct 2014 08:27:32 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WP6528nv8m5hvr5GTj7DEHQi9Vf5gcHp/iwykwGtaVw=; b=NX6N4zMZG015iMPikdGf+NSHfhxAf2dO8teQ6s30G+/Rw8u0g4m0UkNwYYqYj2Tk8V yNlQ6wRkwsMP8woHl5toeES6oJJI4c8d52dYU7xyFvEaFk9M0vug210plJSEOEl1J8SJ gDz+X1p93Gh6nB7rRYyRT70NRvO55AxWiBH+d3cvROzxaO2PpvR+lL1HPZ3629UeQ9F1 d2Q47tq+UoYcWtLgAh/uuPIn9WJuKSB8hJlyQeRRvPShxcC6eqwo2uLKNKRlCVr2IOei WD+DlJcaCOhfLQB5zt7WA8V40TZzDIb95tlmCvCDbWxPh8jqwgfspMTPl3Q7ug1FpbwW YE0Q==
X-Gm-Message-State: ALoCoQmh6VRP3fSCI+RFUIJPZQX/6MrNQh6b0sdzV6gLWZOnNLCZIOj9WhywBKL9xuB5g2Ta74qs
MIME-Version: 1.0
X-Received: by 10.202.225.212 with SMTP id y203mr10834166oig.16.1413386851840; Wed, 15 Oct 2014 08:27:31 -0700 (PDT)
Received: by 10.76.175.234 with HTTP; Wed, 15 Oct 2014 08:27:31 -0700 (PDT)
In-Reply-To: <20141014182611.dd6598cc163e9c640d4167fd@nri.co.jp>
References: <20141014182611.dd6598cc163e9c640d4167fd@nri.co.jp>
Date: Wed, 15 Oct 2014 08:27:31 -0700
Message-ID: <CA+wnMn9Fs3FsNKN2FP_2c=NbeFepgjJaK=+QE2U8--uaLNvuZQ@mail.gmail.com>
From: Chuck Mortimore <cmortimore@salesforce.com>
To: Nat Sakimura <n-sakimura@nri.co.jp>
Content-Type: multipart/alternative; boundary="001a113d2dfe3c29c3050577c531"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/qMsMCfZeS5AXqZXuE8nUKZb1CD0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] SPOP - code verifier requirements
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 15 Oct 2014 15:27:35 -0000

We went with base64url in our implementation

On Tue, Oct 14, 2014 at 2:26 AM, Nat Sakimura <n-sakimura@nri.co.jp> wrote:

> In his mail, Mike asked whether code verifier is
> a value that is sendable without trnasformation
> as a http parameter value, or if it needs to be
> % encoded when it is being sent.
>
> We have several options here:
>
> 1) Require that the code verifier to be a base64url encoded string of a
> binary random value.
>
> 2) Let code verifier to be a binary string and require it to be
> either % encoded or base64url encoded when it is sent.
> In this case, which encoding should we use?
>
> 3) require the code verifier to be conform to the following ABNF:
> code_verifier = 16*128unreserved
> unreserved    = ALPHA / DIGIT / "-" / "." / "_" / "~"
>
> Which one do you guys prefer?
>
> Nat
>
> --
> Nat Sakimura (n-sakimura@nri.co.jp)
> Nomura Research Institute, Ltd.
>
> PLEASE READ:
> The information contained in this e-mail is confidential and intended for
> the named recipient(s) only.
> If you are not an intended recipient of this e-mail, you are hereby
> notified that any review, dissemination, distribution or duplication of
> this message is strictly prohibited. If you have received this message in
> error, please notify the sender immediately and delete your copy from your
> system.
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email