GitHub user aglinxinyuan edited a comment on the discussion: Proposal - Migrating User Authentication to a new table to support multiple log-in sources.
<html> <body> <!--StartFragment--><html><head></head><body><p>Local authentication and third-party authentication should be treated in the same way. We don't need to introduce provider-specific terminology such as <em>OAuth</em>, <em>password</em>, or <em>ID</em>.</p><p>Conceptually, the second table only needs two fields: <strong>provider</strong> and <strong>secret</strong>. The second column can be named <code inline="">password</code>, <code inline="">oauth_id</code>, <code inline="">provider_id</code>, <code inline="">token</code>, or anything similar—it simply stores the credential (i.e., a secret string) used to authenticate the user with that provider. We shouldn't care what technology or stack is behind the provider, as we should always keep the credential secret, whether it's a provider_id or a password hash.</p><p>For example:</p> uid |provider | secret -- |-- | -- 2 |google | 124re4244 2 |local | hash64e2f2f2f24f2f Also, if we only have 3 columns in the second table, we can avoid NULL columns. </body></html><!--EndFragment--> </body> </html> GitHub link: https://github.com/apache/texera/discussions/6716#discussioncomment-17760651 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
