[OAUTH-WG] Questions about oauth-browser-based-apps-06
Jared L Jennings <jaredljennings@gmail.com> Thu, 21 May 2020 03:43 UTC
Return-Path: <jaredljennings@gmail.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 284743A0A6E for <oauth@ietfa.amsl.com>; Wed, 20 May 2020 20:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=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 xcXC14ru_mvj for <oauth@ietfa.amsl.com>; Wed, 20 May 2020 20:43:22 -0700 (PDT)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 A8D593A0A6C for <oauth@ietf.org>; Wed, 20 May 2020 20:43:22 -0700 (PDT)
Received: by mail-oi1-x233.google.com with SMTP id r25so5097913oij.4 for <oauth@ietf.org>; Wed, 20 May 2020 20:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-language; bh=JAsv7mchq8UlAMFjwFuD1ACC9ybfXOdqbqR+uj59zkU=; b=P4z0fNi+evHn15jgU7Rj9uCvI9w2pYCwR4TaRLT/a1cldZtk69HfZDfLLrdvaNrN7i 0x2As83K/nP1vx88lI8cIvRaEdWi+CWNmulJX+jsJXa0tWenX6CrmEpFQw+kj+Es2Krg jT9FnPh1nBsY4LmM6o3PeU0oKf1VvlpKqZDTQqJTbzsP+xONa1oy7wr9EhFrhlVgc0l7 CMrQkYd5NfWNzy8c+FyBzGUw4a01T7XobBHUhaAh/JGnk+ausojDdVGIFYuHBYt5LaaW M7hot6ADMCH39EUxyHpeiuZU88iMBywf2jsvxfcJyl1lQ120cPi96EWfKXRDUojXDaxK JLmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-language; bh=JAsv7mchq8UlAMFjwFuD1ACC9ybfXOdqbqR+uj59zkU=; b=BVXU+4gf1GepqkNt1io7BpkBUT4LQB3gLkzRS6VVuNtasfC1YRgWxSwACUJNN5C7L4 CAkp3qSLYUduNcG8beG3QRb7lGdZFarsDbdAjwC+9qnU3UzyhLp0JqyL1zdajWobHrvk RSXMG4jg/QLAybYONsrufnC1lo1UQYIuEU2SU4g2Xwwd4IXA3+8FEeH+sHpJkfwKHgp/ pILF65zRDRYAMjii0Etohcith4GhiSPubv9gVWB+iq/0vRRl78fLypL2pt4zxVW+Tvf6 eYSYW60mU42ZgEtHfPzgf9vAmOU8WEid+GXkX22rsmCQH4oElOlyiJ3aWbB74xZdy1tl CHTw==
X-Gm-Message-State: AOAM532aUP6CjNtQIc405/8cElnPK4golN5znkZWOfesNgWWix0PKPv2 SleFjbEHEYw2j3t0FCKoBMnSfwFsQic=
X-Google-Smtp-Source: ABdhPJwIsVQFj30O3ia4qme43Q9BZ/MG8LiPf7Y7JAUeBPjMkNLo6IvC3yx8+lGgNtPLCkUWYHJamQ==
X-Received: by 2002:aca:cdc6:: with SMTP id d189mr5740391oig.19.1590032601158; Wed, 20 May 2020 20:43:21 -0700 (PDT)
Received: from jareds-mbp-2.lan ([72.214.170.165]) by smtp.gmail.com with ESMTPSA id g30sm1343966oiy.42.2020.05.20.20.43.19 for <oauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 May 2020 20:43:20 -0700 (PDT)
To: oauth <oauth@ietf.org>
From: Jared L Jennings <jaredljennings@gmail.com>
Organization: Ninja Tools
Message-ID: <c95d2c0f-3a19-8743-06a6-3b6b34fc0fcd@gmail.com>
Date: Wed, 20 May 2020 22:43:13 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------0CC581FCD4977ED7A9C2438E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/BHlU2ZjGLbhDqh5TMfLRn1TSKTU>
Subject: [OAUTH-WG] Questions about oauth-browser-based-apps-06
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: Thu, 21 May 2020 03:43:24 -0000
I'm surprised that this is OK. Why is this safe or a best practice?
/The Application Server can store the access token either server-side, /
/or in the cookie itself./
What are appropriate browser APIs? (Maybe providing some guidance or a
hint regarding this?)
/The JavaScript app is then responsible for storing the access token /
/(and optional refresh token) securely using appropriate browser APIs./
Can the access token be included the various (all) available transport
methods? Query string, Header, Post, etc.
/When the JavaScript application in the browser wants to make a request
to the Resource Server, it can include the access token in the request
(D) and make the request directly./
Thanks,
--
-----
Jared L Jennings
816.678.4152
Skype: jaredljennings
- [OAUTH-WG] Questions about oauth-browser-based-ap… Jared L Jennings