Developer builds Firebase-based e-signature system with OTP, PDF hash, and audit trail
A developer built an internal document acknowledgement system using Firebase, Netlify Functions, and pdf-lib to collect verifiable proof that team members had read and accepted company documents. Rather than using Firebase Phone Auth with SMS OTP, the system generates a 6-digit email OTP server-side, storing only a salted hash in Firestore with a five-minute expiry to cut costs and complexity. Each signed document record captures the user's name, timestamp, server-side IP address, and a client-computed SHA-256 PDF hash, forming a traceable audit trail. The developer deliberately avoided the term 'digital signature' in the UI, noting that under Italy's eIDAS-aligned rules, a qualified digital signature requires an accredited certification authority — something this system does not provide. The solution reuses existing infrastructure including EmailJS and Firebase Storage, adding no new services or extra costs.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in