Return-Path: <panva.ip@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 83E9D1203F5
 for <oauth@ietfa.amsl.com>; Wed,  3 Jul 2019 07:51:16 -0700 (PDT)
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=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 knobr0dnvD-e for <oauth@ietfa.amsl.com>;
 Wed,  3 Jul 2019 07:51:13 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com
 [IPv6:2607:f8b0:4864:20::232])
 (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 EE97D120414
 for <oauth@ietf.org>; Wed,  3 Jul 2019 07:51:10 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id 65so2259827oid.13
 for <oauth@ietf.org>; Wed, 03 Jul 2019 07:51:10 -0700 (PDT)
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=5OGpDAnyqy99GBTdVNN/pxjNukC6NsLaR2IX+sxI9+o=;
 b=hWXhNiD4V/ZEYsSua14a1JlkCtDGkewMh0sA94Opb9GTZx1Ros18TLpxhXX/iNSQOk
 Jczr7mRtU2zpkonNhaddCiKkIjTKCkn0BIZpiigOl7TnatEmNj5R4h9kxF929ldv3nxX
 qDZiBiK7AxLpmbsAbcGrEOiYRLImuvWuwHtANRVKrL1VihenPEBB7JK44wY217+msdKw
 U9lVgyw4ZPufumj3880B/cymfeMaNPx7x5gTAQdSQigTdqS5XBD/yQqa9rQocxehHjDk
 Ktwo/XW8qiKOoKWzxo9L9rpMxNdvoazofmLBuaQa9EasRrsmfDk4upP8e3nGn6vIrsqp
 IrQA==
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=5OGpDAnyqy99GBTdVNN/pxjNukC6NsLaR2IX+sxI9+o=;
 b=U6etOrVohRu9qiubmbnkkPloI+VtZXf9A4c5FxAgRFkvPb1qFOZGp7f4mrgeBPE6yQ
 fAXaTVBctxSEfJ90IUIZiGsdvZP4Fv15Ueg25ktkF4Zy8H7wBkebOqj+GfmW0a8KfVX5
 ClZH/9dJqtAvr02miQKapasyK6dyUgQZsw2HlqNlzgQTJXz2SxsEZ08EjbLqQ1v/iUx4
 8TdOPKK05Icw1AAWIh89uGY3NcKomXvC0TxIRSTv3jOHEesSoOit3iHdm19xjuEY7yRI
 vksQywDtVWnmkQjIMSv6Gehlcft7Js62PJ7kPVqrkXRZm/x9ZMYAqL50IXstCoC+6mCa
 S0Ng==
X-Gm-Message-State: APjAAAWfZqXWTR2DMZyi2OWDNNMfO920Clj4SRxLmGXWH3JtdnzK1PRA
 Ou3xyKxaneqcWGD0p4gaK93j7wM1i8xXS22c+braCS6pvIim
X-Google-Smtp-Source: APXvYqxNn4uW1CiI04WmXSEFJf+2QjimQ1/KJf4B9zhzTM8dNuqclx4yrqLxwoLUDaH8ZVZIaFHqBHocinhKGASjASM=
X-Received: by 2002:aca:cc49:: with SMTP id c70mr3947723oig.174.1562165470019; 
 Wed, 03 Jul 2019 07:51:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAF2Zz1Q-F26d=B41v8B+Qr25z9LuTWd5XEC-fgHAzs_7bhvTuQ@mail.gmail.com>
In-Reply-To: <CAF2Zz1Q-F26d=B41v8B+Qr25z9LuTWd5XEC-fgHAzs_7bhvTuQ@mail.gmail.com>
From: Filip Skokan <panva.ip@gmail.com>
Date: Wed, 3 Jul 2019 16:50:58 +0200
Message-ID: <CALAqi__tFP7biYyjbNJVp_uCG1ermE4uAbQK4x6kEtOv9QYFQw@mail.gmail.com>
To: Daniel Roesler <daniel=40utilityapi.com@dmarc.ietf.org>, 
 "Donald F. Coffin" <dcoffin@greenbuttonalliance.org>
Cc: OAUTH-WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ebc542058cc7fdb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/cySo9tP550sRUaajMP3u79w-WmQ>
Subject: Re: [OAUTH-WG] OAuth 2.0 UI/UX Resources?
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: Wed, 03 Jul 2019 14:51:21 -0000

--000000000000ebc542058cc7fdb6
Content-Type: text/plain; charset="UTF-8"

Hello Daniel,

you may gather inspiration and explore Auth0's flows all-in-one page at
https://flows.auth0.com

Best,
*Filip Skokan*


On Wed, 3 Jul 2019 at 16:26, Daniel Roesler <daniel=
40utilityapi.com@dmarc.ietf.org> wrote:

> Howdy all,
>
> Apologies if this is slightly off topic.
>
> I'm a part of the Green Button Alliance, the non-profit standards body
> around sharing energy data, and the customer consent process is based
> on OAuth 2.0 (e.g. granting access to your smart meter data in order
> to have an energy audit done).
>
> However, most utilities we work with are unfamiliar with OAuth 2.0, so
> we often have to explain how it works and what the best practices are.
> There are plenty of resources we can point them to for the actual
> protocol handshake, but I haven't been able to find any resources
> around best practices for designing the user interface and experience
> of OAuth. Unfortunately, in the energy industry, UI/UX design isn't
> our strong suit, so it would be very helpful if we had design
> lessons-learned from other industries to use as a reference.
>
> Does anyone here know of any resources, talks, blog posts, examples,
> etc. for making good OAuth 2.0 UI/UX?
>
> Thanks!
> Daniel Roesler
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

--000000000000ebc542058cc7fdb6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hello Daniel,<div><div><br></div><div>you=
 may gather inspiration and explore Auth0&#39;s flows all-in-one page at=C2=
=A0<a href=3D"https://flows.auth0.com">https://flows.auth0.com</a></div><di=
v><br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature" data-sm=
artmail=3D"gmail_signature">Best,<br><b>Filip Skokan</b></div></div><br></d=
iv></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Wed, 3 Jul 2019 at 16:26, Daniel Roesler &lt;daniel=3D<a href=
=3D"mailto:40utilityapi.com@dmarc.ietf.org">40utilityapi.com@dmarc.ietf.org=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
Howdy all,<br>
<br>
Apologies if this is slightly off topic.<br>
<br>
I&#39;m a part of the Green Button Alliance, the non-profit standards body<=
br>
around sharing energy data, and the customer consent process is based<br>
on OAuth 2.0 (e.g. granting access to your smart meter data in order<br>
to have an energy audit done).<br>
<br>
However, most utilities we work with are unfamiliar with OAuth 2.0, so<br>
we often have to explain how it works and what the best practices are.<br>
There are plenty of resources we can point them to for the actual<br>
protocol handshake, but I haven&#39;t been able to find any resources<br>
around best practices for designing the user interface and experience<br>
of OAuth. Unfortunately, in the energy industry, UI/UX design isn&#39;t<br>
our strong suit, so it would be very helpful if we had design<br>
lessons-learned from other industries to use as a reference.<br>
<br>
Does anyone here know of any resources, talks, blog posts, examples,<br>
etc. for making good OAuth 2.0 UI/UX?<br>
<br>
Thanks!<br>
Daniel Roesler<br>
<br>
_______________________________________________<br>
OAuth mailing list<br>
<a href=3D"mailto:OAuth@ietf.org" target=3D"_blank">OAuth@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/oauth" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/oauth</a><br>
</blockquote></div></div>

--000000000000ebc542058cc7fdb6--

