<div dir="ltr">No there isn't anything like that. Sounds like a potential hackers heaven as well.<div><br></div><div>Assuming you've got the idea from WildFly. WildFly can do that by writing to a local file to make sure the user is indeed on the local machine. That doens't work in a web based flow unless you can find a way to "share" a file between the Keycloak server and the browser.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 September 2016 at 17:17, Jess Sightler <span dir="ltr"><<a href="mailto:jsightle@redhat.com" target="_blank">jsightle@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there a builtin authenticator that can provide a default user account<br>
based upon some criteria? For example, could we provide a default user<br>
if the client is connecting to localhost?<br>
<br>
______________________________<wbr>_________________<br>
keycloak-user mailing list<br>
<a href="mailto:keycloak-user@lists.jboss.org">keycloak-user@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-user" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/keycloak-user</a><br>
</blockquote></div><br></div>