Re: [keycloak-dev] browser refresh again

Do we support async authenticators? I'm thinking about something like: * User logs in on desktop with username/password * As two factor auth we send a notification to a mobile phone app * When user clicks ok on the mobile phone app the login on the desktop continues This type of authentication is used by banks in Norway, which is very nice as you don't need to manually write a code. On 13 January 2016 at 22:34, Bill Burke <bburke(a)redhat.com <mailto:bburke@redhat.com>> wrote: I'm changing browse refresh behavior again. I've removed all the extra redirects, so now, you can end up being on the OTP page, but the URL is the one posted to by password page. Refresh page will repost the password, keycloak will see that the current action is not the same, and just ask the flow to put the browser in the right state. Similarly with required actions. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-dev