refactor(security): create consistent HMAC token implementation #67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, we (re)create the HMAC token code in various places (OTP, email, invitatoins for example). It would be good to consolidate this code in a refactor, with special attention to security considerations