Re: [keycloak-user] [development] Jumping to another flow from an authenticator

Hi, Thanks for your answer! Yeah sure, I try to use the add-user.sh which is intended for that: https://www.keycloak.org/docs/2.4/server_installation_guide/topics/operat... But I can´t get the Slave connected to the Master, in the Wildfly Docu a username in domain.xml is mentioned, but if I try to add that attribute I´ll get an "not supported" error in Keycloak. So my question is how does keycloak determine the correct user the slave uses? The Wildfly docu mentions that if omitted the hostname is used. I tried that but still get a not authorized error. What should I do? :) Greetings Marc -----Ursprüngliche Nachricht----- Von: keycloak-user-bounces(a)lists.jboss.org [mailto:keycloak-user-bounces@lists.jboss.org] Im Auftrag von Marek Posolda Gesendet: Monday, April 10, 2017 9:42 PM An: Tomás García <tomas(a)intrahouse.com>; keycloak-user(a)lists.jboss.org Betreff: Re: [keycloak-user] [development] Jumping to another flow from an authenticator I think it's possible with current implementation by using: context.forkWithSuccessMessage("some message, which will displayed on the initial login screen"); or also "context.forkWithErrorMessage" . The "context" references AuthenticationFlowContext object passed to the authenticator. Something like this is used at ResetCredentialEmail authenticator, which is used during reset-credentials flow (when user press link "Forget my password" on the login screen). Hope this helps, Marek On 10/04/17 15:56, Tomás García wrote: _______________________________________________ keycloak-user mailing list keycloak-user(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user