FeatureFuel
1

A way to specify user authentication strategy

Source: supabase/supabase#1718 · opened by @Sid-Sun
I recently started workings on creative a notes API, I have a security background and wanted to have encryption on the data - I have a custom protocol for authentication users, it can be summarised as: When user signs up, I create a random key used for encryption of their data, this key is encrypted with the user's password and stored in the database When user logs in I fetch the encrypted key, decrypt it and if it is valid then user is authenticate and the key is them used for encryption / decryption of user data I want to use Supabase in the project, Supabase provides its own authentication system but that won't allow me to implement my protocol without at least adding another layer of redundancy in authentication (fetch key & decrypt key after login is successful) additionally, the part I like about my approach is user's password is not stored in any form (including hashes) so it can be guaranteed only they can access their data Being able to provide Supabase…

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests