I suppose you've implemented custom SPI execution [1],
Then in admin console in "Authentication" tab you should make a
copy of "Registration" flow. Then you have to add new execution
[Actions -> Add execution] (your custom execution with sms
validation) to "Copy Of Registration Registration Form" and then
you make the execution "REQUIRED".
Already did this. My point is that the default registration steps
combined with a custom one can't be an atomic operation. User entity
is created on the first step without fully passing through the flow.
I'd need to investigate this further. Do you have any reproducer which
may be used to simulate your issue?
V.
On Fri, 12 Apr 2019 at 12:14, Vlasta Ramik <vramik(a)redhat.com
<mailto:vramik@redhat.com>> wrote:
On 4/12/19 10:49 AM, Pavel Drankov wrote:
>
> registration should be an atomic
>
> Sure, I agree with you. But, a user is created after the first
> step by default. How can I make the user creation process
> consisted of two steps atomic?
I suppose you've implemented custom SPI execution [1],
Then in admin console in "Authentication" tab you should make a
copy of "Registration" flow. Then you have to add new execution
[Actions -> Add execution] (your custom execution with sms
validation) to "Copy Of Registration Registration Form" and then
you make the execution "REQUIRED".
[1]
https://www.keycloak.org/docs/latest/server_development/index.html#_provi...
>
> Best wishes,
> Pavel
>
>
> On Fri, 12 Apr 2019 at 09:54, Vlasta Ramik <vramik(a)redhat.com
> <mailto:vramik@redhat.com>> wrote:
>
> Hey Pavel,
>
> inline
>
> On 4/10/19 5:36 PM, Pavel Drankov wrote:
> > Hello,
> >
> > I'm trying to implement a two-step registration process
> based keylock. On
> > the first step enters the same information as in the
> default registration
> > form, but with the addition of telephone number. On the
> second step, he
> > enters a code received via an SMS message.
> >
> > The problem I faced is that if a user successfully filled
> the first step
> > registration form and failed to enter a valid code on the
> second step, he
> > is not able to use the same email address on the first
> step(because of "Email
> > already exists." error). Is there a way to clean up not
> fully registered
> > users and allow them to re-register if they have not
> finished all the step
> > from the registration flow.
>
> It doesn't sound right, I think the registration should be an
> atomic
> operation, so either both steps are successful and user is
> registered or
> the user is not registered.
>
> To tell more I'd need to know more information how you've
> developed the
> described functionality.
>
> Regards,
>
> V.
>
> >
> > Best wishes,
> > Pavel
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user(a)lists.jboss.org
> <mailto:keycloak-user@lists.jboss.org>
> >
https://lists.jboss.org/mailman/listinfo/keycloak-user
>