EventListner after user Registration

[Venugopal Puttaramaiah]

Scenario:
after user registration is successful, the user will receive a verification email.

which he has to verify within specified time.

else {

this is my scenario, as keycloak does not support follow up email. (or resend of email) 
my schedule task, triggers after a registration event (when a new user registers).

The task will check if VERIFY_EMAIL is true or not, 

if NOT, then send an email asking him to redo the registration.  

}

below is the sample java code.
can we have this business requirement implemented in key Cloak itself. ?

[Alexander Schwartz]

Hi Venugopal,

as you are asking help to write an extension, and this message is not about contributing to Keycloak itself, please use the keycloak user mailing list instead. 

https://groups.google.com/g/keycloak-user

Best,

Alexander

--
You received this message because you are subscribed to the Google Groups "Keycloak Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keycloak-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/keycloak-dev/30841b08-3bc4-49e8-9f0b-2be13f96a92dn%40googlegroups.com.

--

Alexander Schwartz, RHCE

He/Him

Principal Software Engineer, Keycloak Maintainer

Red Hat - Germany remote

asch...@redhat.com   

Red Hat GmbH, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany 
Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,
Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross

[Venugopal Puttaramaiah]

where to send the code to contribute ? 

[Alexander Schwartz]

Sorry, I mis-read your email, and I see you want to contribute this to Keycloak.

Yes, this is developer list is the place to ask for. 

I see you managed to implement this as an extension. As this solves your need, you might install it as an extension. If you want others to use it, you can publish it as an extension: https://www.keycloak.org/extensions

Looking at your implementation, it would work with short time frames of 120 seconds, as AFAIK the scheduled talk will not survive a server restart. A cyclic task that picks up any not-yet-confirmed entries from the database after a restart would make this IMHO complete. 

If you see this becoming a popular extension, and more people asking for it to become a core functionality, please create GitHub enhancement issue and a pull request. 

Best,

Alexander