You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The event IDENTITY_PROVIDER_FIRST_LOGIN can be useful, if one would like to trigger some action whenever there is one (by creating a custom EventListenerProvider), or simply for auditing purposes by storing it.
try logging in using the identity provider you configured
Go back to the admin console -> and check the events that got triggered.
You will find the following events:
CODE_TO_TOKEN
LOGIN
REGISTER
but not the IDENTITY_PROVIDER_FIRST_LOGIN
Anything else?
This can be fixed simply by adding event.success() (checkout the PR for more details)
The only thing to note is that the user is not created yet at this point, so the user field in the event will be null / empty. Here is an example entry:
The text was updated successfully, but these errors were encountered:
Describe the bug
The event
IDENTITY_PROVIDER_FIRST_LOGIN
can be useful, if one would like to trigger some action whenever there is one (by creating a custom EventListenerProvider), or simply for auditing purposes by storing it.It seems like the event is used here: https://github.com/keycloak/keycloak/blob/main/services/src/main/java/org/keycloak/services/resources/LoginActionsService.java#L759
However, it seems like the event is never triggered because the
.success()
method is never called.Version
19.0.2
Expected behavior
The
IDENTITY_PROVIDER_FIRST_LOGIN
should be triggeredActual behavior
The
IDENTITY_PROVIDER_FIRST_LOGIN
is not triggeredHow to Reproduce?
You will find the following events:
but not the IDENTITY_PROVIDER_FIRST_LOGIN
Anything else?
This can be fixed simply by adding
event.success()
(checkout the PR for more details)The only thing to note is that the user is not created yet at this point, so the user field in the event will be null / empty. Here is an example entry:
The text was updated successfully, but these errors were encountered: