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
Recently I had the situation where we wanted to customise the format of the recovery codes generate by Fortify. As RecoveryCode::generate() is called statically I had to extend a couple of actions and the TwoFactorAuthenticatable trait and override some methods to be able to call my own RecoveryCode class.
I can make a PR to make this more configurable, but I was wondering people's thoughts on binding RecoveryCode to the container vs. having a Fortify::generateRecoveryCodesUsing() method that could be placed in a service container?
Cheers,
Tom.
The text was updated successfully, but these errors were encountered:
Hi,
Recently I had the situation where we wanted to customise the format of the recovery codes generate by Fortify. As
RecoveryCode::generate()
is called statically I had to extend a couple of actions and the TwoFactorAuthenticatable trait and override some methods to be able to call my own RecoveryCode class.I can make a PR to make this more configurable, but I was wondering people's thoughts on binding RecoveryCode to the container vs. having a
Fortify::generateRecoveryCodesUsing()
method that could be placed in a service container?Cheers,
Tom.
The text was updated successfully, but these errors were encountered: