# AI wrote my login in 10 minutes. The rest of auth is the expensive part — retained record

> Retained reddit record from reddit:SaaS.

Canonical: https://highsignal.app/data/records/e262e45cde880f95

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:SaaS)  published 2026-10-25 18:21 ingested 2026-10-26 02:37

[original source ↗](https://www.reddit.com/r/SaaS/comments/1xf9ojs/ai_wrote_my_login_in_10_minutes_the_rest_of_auth/)

## retained text



```
As a founder, it's tempting to have an assistant generate auth and move on. I tried it. The happy path worked right away. What it didn't include unless I asked: lockout, enumeration-safe errors, session revocation after a password change, refresh-token rotation, MFA recovery, safe password reset, and GDPR erasure that keeps an audit trail.

Those gaps don't throw errors. They show up in a security questionnaire from your first enterprise customer, or in an incident.

Two data points I found useful:

\- Veracode 2026: \~56% security pass rate across 100+ models, barely moved from last year

\- Stanford: devs with AI assistants wrote less secure code and were more confident in it

My takeaway: use AI for prototypes, integration code, and checklist-driven review. Don't let it be the only author of your credential store, and don't let every new service grow its own users table.

Disclosure: I'm building P'adentro, a self-hosted auth backend, so I have skin in this game.

Write-up with sources: https://padentro.dev/blog/ai-can-write-your-login-should-it-own-your-auth

How did you handle auth in your SaaS: buy, build, or self-host?
```



document fetched 2026-10-26 00:27 · canonical https://reddit.com/r/SaaS/comments/1xf9ojs/ai_wrote_my_login_in_10_minutes_the_rest_of_auth
