Thanks, Marek.
That did the job. I tried with context.fork() and it worked too, without
the need to set a message.
On Mon, Apr 10, 2017 at 8:42 PM Marek Posolda <mposolda(a)redhat.com> wrote:
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:
Hi,
I'm doing experiments with authenticators... I've made an authenticator for
the "first broker login" flow and I'm wondering if, under certain
condition
I implemented inside the authenticateImpl method of the authenticator, I
can jump to the browser flow to "challenge" the user with the regular login
screen. It looks like it's impossible by design.
If there's another alternative, you can think about, it would be great.
Thanks.
_______________________________________________
keycloak-user mailing
listkeycloak-user@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/keycloak-user