Menu

Self-taught dev retrofitting Passkeys/WebAuthn into legacy PHP app - architecture advice?

Reddit r/webdev·u/jjswin·6 months ago
#dfwD88Kq
#auth#passkeys#architecture#self#taught
Reading 0:00
15s threshold

Self taught developer here, so apologies if I’m misunderstanding some fundamentals.

I’ve built a fairly large custom PHP 8.3 + MariaDB app over time with traditional session/cookie auth across multiple subdomains. It works fine currently with passwords.

I’m now trying to implement Apple Passkeys/WebAuthn and I’m hitting what feels like architectural problems rather than coding bugs. I don’t want to get into the issue really here.

I think I may be trying to retrofit modern auth onto an older architecture in the wrong way.

My questions are more conceptual than code-specific:

* In 2026, what’s considered the “correct” architecture for passkeys in a traditional PHP app?

* Should auth be centralised onto one auth subdomain/service?

* Are server-side sessions still fine, or should I be thinking token/JWT style auth?

* Is passkey-first/passwordless realistic for a non-framework PHP app?

Would really appreciate advice from people who’ve implemented this in production, especially if you came from older PHP…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.