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
When an Auth0 user is manually deleted and re-created (e.g. when testing), the createUser operation will either:
Throw an error, when using the production KMS server.
Update the Auth0 user with owner and walletAddress properties that do not match the RSA keys that were previously created in Google KMS.
We should:
Add checks to verify the keys in Google KMS and the ones in the Auth0 user match (probably in the server middleware).
Update the user creation logic to avoid/skip key creation if they already exist, which would also allow users who experienced some kind of error or malfunction when trying to create an user to try again (with the current implementation, they might be locked out).
When an Auth0 user is manually deleted and re-created (e.g. when testing), the
createUser
operation will either:owner
andwalletAddress
properties that do not match the RSA keys that were previously created in Google KMS.We should:
Related to #15 (comment).
The text was updated successfully, but these errors were encountered: