Mk
/
supersam
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(login): request-otp must insert otp_code (NOT NULL) for send_pin email 

Full edge-fn sync clobbered a live hotfix: repo request-otp only wrote
otp_code_hash, but login_otps.otp_code is NOT NULL, so every request
failed with 'Failed to generate OTP' and no PIN email was sent. Restore
writing otp_code (n8n send_pin trigger emails it; verify still uses hash).
This commit is contained in:
Hermes 2026-08-21 16:35:04 +02:00
parent a505ce6ca7
commit 2fda27a329
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
supabase/functions/request-otp/index.ts
View File

@ -89,11 +89,14 @@ Deno.serve(async (request) => {
const clientIp = getClientIp(request); const clientIp = getClientIp(request);
const userAgent = request.headers.get("user-agent") || null; const userAgent = request.headers.get("user-agent") || null;
// Insert with OTP hash only — no plaintext in DB // Insert with OTP hash for verification. otp_code (plaintext) is also stored
// because DB has it NOT NULL and the send_pin trigger (→ n8n webhook) emails
// this exact code to the user. verify-otp still compares the SHA-256 hash.
const { error: insertError } = await supabase.from("login_otps").insert({ const { error: insertError } = await supabase.from("login_otps").insert({
email, email,
name: userName, name: userName,
role: userRole, role: userRole,
otp_code: otp,
otp_code_hash: otpCodeHash, otp_code_hash: otpCodeHash,
ip_address: clientIp, ip_address: clientIp,
user_agent: userAgent, user_agent: userAgent,