Our social identity providers require an import of the user right now. You can hook into this flow and interact with the legacy system in the background if you want. On 6/29/16 12:08 PM, Chris Hairfield wrote: I don't expect this is possible, but does anyone know whether one can prevent new account creation when Identity Brokering with Facebook and Google while still allowing sign-in? We are attempting to migrate our legacy IDM solution to Keycloak slowly and wish, for the time being, for all new account creation to still go through the legacy app. We have HAProxy in front of Keycloak. Is there a way to redirect users attempting to join via Facebook or Google to our legacy join page? _______________________________________________ keycloak-user mailing listkeycloak-user@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-user _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user