Having to setup an admin login and passing that into the environment is a process that causes some friction to users and contributors. It is different for each provider, and needs to be tested.
By switching to passkeys that are generated on first login (https://github.com/lbuchs/WebAuthn?tab=readme-ov-file) we create a more secure derived credential that cannot be copied or stolen, that is managed by the password manager that should be less friction and more robust.
As a rule Lamb does not maintain multiple implementations and with hardly any real world code out there it's fine to make this a breaking change.
Questions
[ ] can I programmatically create one to bootstrap tests?
Having to setup an admin login and passing that into the environment is a process that causes some friction to users and contributors. It is different for each provider, and needs to be tested.
By switching to passkeys that are generated on first login (https://github.com/lbuchs/WebAuthn?tab=readme-ov-file) we create a more secure derived credential that cannot be copied or stolen, that is managed by the password manager that should be less friction and more robust.
As a rule Lamb does not maintain multiple implementations and with hardly any real world code out there it's fine to make this a breaking change.
Questions