Skip to content

DR:0006‐ Auth DB provider for doula onboarding

Hunain Bin Sajid edited this page Dec 10, 2024 · 1 revision

Decision Record: Authentication & DB provider Date: 2024-12-10 Status: Accepted Deciders: AS, EG, HS, LB, TB Tags: #data, #mvp, #backend

Context How should the MVP store and handle user-submitted documents and data (e.g., certification PDFs)?

Alternatives Considered

Option A: Auth2 - Use a third-party auth/db provider (🚩) Pros: Simple and fast to implement for MVP. Cons: Potential data security and privacy issues; unaligned with credential-based access.

Option B: Auth2 - Develop a trivial token-based auth service rooted in db

Pros: More control over data Cons: Higher complexity and upfront effort, do not align with the long-term vision of credential-based access

Option C: Auth3 - Develop a custom credential-based backend

Pros: Aligns with vLEI vision; leverages existing tooling from Reg Pilot. Cons: Higher complexity for non-technical users; might require custodial approaches initially.

Decision

Use a third-party auth/db service for POC/MVP, with the aim of changing it to credential-based access (Option C) later.

Follow-Up Actions

Integrate web app with a third-party backend service provider