Hey everyone! Hope you’re all having a great day s...
# ktor
a
Hey everyone! Hope you’re all having a great day so far. I was planning to use Ktor for a new product we’re building at work, but I realized it doesn’t have built-in support for WebAuthn/passkeys. That got me curious, so I started looking into how Spring Security handles it, since our other services are built with Spring. I also explored similar implementations in the Swift ecosystem. After digging into it for a couple of days, I started putting together a proposal to add native WebAuthn/passkey support to Ktor, following the KLIP process. My goal is to make WebAuthn/passkey authentication secure by default, with an API that feels natural in Kotlin and lets developers integrate passkeys without unnecessary boilerplate or configuration. Before taking this any further, I’d love to hear what the maintainers think. Is this something you’d be interested in adding to Ktor? Are there any architectural considerations or limitations I should be aware of before moving forward?
nice spin 2
a
cc @Oleh Pantus and @Bruce Hamilton
kodee loving 1
o
Hi @Amir Golmoradi! Yeah, we are interested in this and there is an issue KTOR-5561 Support WebAuthn (FIDO2) Some time ago I’ve created a very draft KLIP for webauthn support on server github.com/ktorio/ktor-klip/pull/5, but OpenID and SAML have higher priority You can add comments on that KLIP, or create completely different one The feature is not planned yet for 3.7.0 or further minors
Are there any architectural considerations or limitations
Idk, I would start with JVM server only, and try to minimize dependancies Also, would be nice if works well with new typed authentication
a
Thanks, @Oleh Pantus ! That's really helpful. Starting with JVM server support makes sense. I'll narrow the initial scope to that, keep dependencies minimal, and make sure the design integrates naturally with the new typed authentication API. I've already started outlining the proposal, so I'll revisit the architecture with those considerations in mind and share a more concrete draft for feedback before moving into implementation.
thank you frog 1
kodee loving 1