-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Spomky webauthn dependencies #175
base: main
Are you sure you want to change the base?
Conversation
76d410a
to
ea71576
Compare
ea71576
to
f84595d
Compare
Also removed the custom internal controller logic. So when the Webauthn flow is started it will be completely handled by the bundle and the configuration can be used without hassle.
f84595d
to
aca0dea
Compare
$nameId = $event->getUser()->name; | ||
$logger = WithContextLogger::from($this->logger, ['nameId' => $nameId]); | ||
|
||
if ($routeName == 'webauthn.controller.security.main.creation.result') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible to use constant? (also in twig)
$this->write("<info>Migating: {$id}</info>"); | ||
|
||
$transports = json_encode(unserialize($transports), JSON_THROW_ON_ERROR); | ||
$otherUi = json_encode(unserialize($otherUi), JSON_THROW_ON_ERROR); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How resilient should this migration be?
If we're talking about a couple of thousand rows, this is fine.
If millions, maybe catch the exception and continue, so it can continue where it left off if the first attempt to migrate everything fails.
Also removed the custom internal controller logic.
So when the Webauthn flow is started it will be
completely handled by the bundle and the configuration
can be used without hassle.