<div dir="ltr">We'd probably also need to either use async servlet requests or websockets as well. Otherwise we could run out of available connections.</div><div class="gmail_extra"><br><div class="gmail_quote">On 14 January 2016 at 15:17, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
To make this work, we would need a way to plug in a REST service
that could receive input from the mobile device. It would search
through client sessions of the user to see which one was waiting for
a mobile authentication. Then change the state of the client
session. The browser session could poll the client session until a
flag was set.<div><div class="h5"><br>
<br>
<br>
<div>On 1/14/2016 2:53 AM, Stian Thorgersen
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Do we support async authenticators? I'm thinking
about something like:
<div><br>
</div>
<div>* User logs in on desktop with username/password</div>
<div>* As two factor auth we send a notification to a mobile
phone app</div>
<div>* When user clicks ok on the mobile phone app the login on
the desktop continues<br>
</div>
<div><br>
</div>
<div>This type of authentication is used by banks in Norway,
which is very nice as you don't need to manually write a code.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 13 January 2016 at 22:34, Bill Burke
<span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm
changing browse refresh behavior again.<br>
<br>
I've removed all the extra redirects, so now, you can end up
being on<br>
the OTP page, but the URL is the one posted to by password
page. Refresh<br>
page will repost the password, keycloak will see that the
current action<br>
is not the same, and just ask the flow to put the browser in
the right<br>
state. Similarly with required actions.<br>
<span><font color="#888888"><br>
--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" rel="noreferrer" target="_blank">http://bill.burkecentral.com</a><br>
<br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</font></span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre cols="72">--
Bill Burke
JBoss, a division of Red Hat
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a></pre>
</div></div></div>
</blockquote></div><br></div>