Note about possible encryption of passkey secrets
Some checks are pending
/ test (push) Waiting to run
Some checks are pending
/ test (push) Waiting to run
This commit is contained in:
parent
0fa8f4f7be
commit
a6bcbaf5e9
1 changed files with 8 additions and 0 deletions
|
@ -14,6 +14,14 @@ import (
|
||||||
"git.mstar.dev/mstar/linstrom/storage-new/models"
|
"git.mstar.dev/mstar/linstrom/storage-new/models"
|
||||||
)
|
)
|
||||||
|
|
||||||
|
// TODO: Check if passkey encryption is viable
|
||||||
|
// Check if encryption for passkey info data is viable to implement
|
||||||
|
// and if we should do it.
|
||||||
|
// Encrypting it would probably require making a custom wrapper struct,
|
||||||
|
// if even possible. Reason being that login completion still requires to update
|
||||||
|
// the data post-creation, including matching on unique and stable elements
|
||||||
|
// of said data
|
||||||
|
|
||||||
// Start the login process via passkey for a given username.
|
// Start the login process via passkey for a given username.
|
||||||
// Returns the credential options the passkey needs to sign
|
// Returns the credential options the passkey needs to sign
|
||||||
func (a *Authenticator) StartPasskeyLogin(
|
func (a *Authenticator) StartPasskeyLogin(
|
||||||
|
|
Loading…
Reference in a new issue