<div dir="ltr">Same here. If there really is a need, perhaps we can start contemplating a way to do it. </div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 30, 2018 at 10:19 AM Brock Allen <<a href="mailto:brockallen@gmail.com">brockallen@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id="m_-5585533778388257960__MailbirdStyleContent" style="font-size:10pt;font-family:Lucida Console;color:#000000">
Suresh --<div><br></div><div>Can you elaborate on your scenarios where a SPA (client-side browser based application) would need to maintain access tokens longer than the user's browser session?</div><div><br></div><div>I'm very curious. <span style="font-size:10pt;line-height:1.5">Thanks.</span></div><div><div><br></div><div class="m_-5585533778388257960mb_sig"><span style="font-family:Lucida Console">-Brock</span><div><br></div></div><blockquote class="m_-5585533778388257960history_container" type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px">
<p style="color:#aaaaaa;margin-top:10px">On 7/29/2018 6:38:29 PM, SureshAtt via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:</p><div dir="ltr">Hello Nat and David,<div><br></div><div>Thanks a lot for your replies. As David mentioned there is already a need for SPA to get longer access to user resources and I have seen different project solves this problem in different ways (ex: using iframes). This led me to think if hybrid flow was desinged to handle this issue as well using refresh tokens, but now I am clear it is not. </div><div><br></div><div>Thanks & regards,</div><div>Suresh Attanayake</div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 29, 2018 at 7:39 AM Nat Sakimura <<a href="mailto:sakimura@gmail.com" target="_blank">sakimura@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks. <div><br></div><div>I made a reply with too much haste as I was about to go out then but the point is this: </div><div><br></div><div>As 10.4 of RFC6749 states: </div><div><br></div><div><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"> The authorization server MUST maintain
the binding between a refresh token and the client to whom it was
issued. </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">The most common and safe way of achieve it is to have </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">the client authenticate to the authorization server. </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">Thus, the client has to be a confidential client, </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">i.e., the client that can keep the confidentiality of its key so that </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">it can use a sender constrained tokens) </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">effectively. </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">(Note: RFC6749 does not define confidential client. </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">Public client is defined slightly better but it still is sloppy like </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">native applications are public client -- well, what if they did a dynamic registration </pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">to get a per-client secret? IMHO, these should be fixed.)</pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial">So, getting back to <span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Suresh's question, it is the intent of the authors not to allow the Javascript </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">clients on a web browser to get refresh token. If the client is effectively a confidential client </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">e.g., by using Token Binding, then, it in principle should be able to make use of a </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Token Bound refresh token, although, it kinds of infringes on RFC6749. </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I suppose the OAuth Token Binding spec should update that bit. </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Best, </span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;white-space:normal;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Nat Sakimura</span></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><pre class="m_-5585533778388257960m_-8999032792951005369gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0);text-decoration-style:initial;text-decoration-color:initial"><br></pre><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 29, 2018 at 12:36 PM David Waite <<a href="mailto:david@alkaline-solutions.com" target="_blank">david@alkaline-solutions.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> On Jul 28, 2018, at 6:32 PM, Nat Sakimura via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" target="_blank">openid-specs-ab@lists.openid.net</a>> wrote:<br>
<br>
<snip><br>
> A public client cannot get refresh token. <br>
> Assuming that you mean "a client working within a browser using JavaScript" by "a JavaScript Client" since it is a public client, it cannot get a refresh token. <br>
<br>
I’m not familiar with this restriction, my understanding is that it is valid and in fact not uncommon for public clients to get and use refresh tokens. RFC 6749 for example does not state such a restriction, and even language around differing behavior with confidential clients vs public clients:<br>
<br>
"Because refresh tokens are typically long-lasting credentials used to<br>
request additional access tokens, the refresh token is bound to the<br>
client to which it was issued. If the client type is confidential or<br>
the client was issued client credentials (or assigned other<br>
authentication requirements), the client MUST authenticate with the<br>
authorization server as described in Section 3.2.1”<br>
<br>
There are quite legitimate reasons for public clients to have refresh tokens, and quite a few mobile apps which already are using refresh tokens.<br>
<br>
With SPA clients for instance, it allows you to extend access without hidden Iframe tricks (and thus could be a workaround to ITP 2.0 blocking state access on XHR / frames / non-interactive redirects, and such forms of cross-domain access causing IDPs to be flagged as trackers)<br>
<br>
-DW</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-5585533778388257960m_-8999032792951005369gmail_signature" data-smartmail="gmail_signature">Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-5585533778388257960gmail_signature" data-smartmail="gmail_signature">Suresh Attanayake<br><br>Blog : <a href="http://sureshatt.blogspot.com/" target="_blank">http://sureshatt.blogspot.com/</a> <div>Web : <a href="http://www.ssoarcade.com/" target="_blank">http://www.ssoarcade.com/</a><br>LinkedIn : <a href="http://www.linkedin.com/pub/suresh-attanayake/16/165/181" target="_blank">http://www.linkedin.com/pub/suresh-attanayake/16/165/181</a> <br>Twitter : <a href="http://twitter.com/sureshatt" target="_blank">http://twitter.com/sureshatt</a> <br></div><div>Facebook : <a href="https://www.facebook.com/IdentityWorld" target="_blank">https://www.facebook.com/IdentityWorld</a></div></div>
_______________________________________________
Openid-specs-ab mailing list
<a href="mailto:Openid-specs-ab@lists.openid.net" target="_blank">Openid-specs-ab@lists.openid.net</a>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a>
</blockquote>
</div></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div></div>