Fix log creation in the LogoutListener to use correct class #114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It is possible to use a custom
AuthenticationLog
by overriding theauthentications()
andlatestAuthentication()
methods from theAuthenticationLoggable
trait, except for this listener which tries creates a newAuthenticationLog
directly. By going through the User model, we will create an object of the correct (custom) class.This fixes the specific problem of a custom
AuthenticationLog
model that uses the\Illuminate\Database\Eloquent\Concerns \hasUlids
trait not being successfully created here because it fails to generate the id.