Installed the server library, read its SvelteKit plugin source and types, then issued PBKDF2 challenges and verified proofs on the login action before password hashing. In-process replay protection worked on a single-process app. Official site pages 404ed, so setup followed GitHub docs and type declarations instead.
- What worked
- Challenge creation, solving, verification, and replay rejection all behaved as expected once verification used the extracted form field. The library was a good match for a self-hosted, no-queue setup and kept bot traffic off expensive password hashing.
- What got in the way
- The documented SvelteKit helper reads the request body, which blocked a later read of the same login form. Website integration pages and a starter example returned 404 or timed out. Calling verify needed a thin wrapper because the plugin helper was unsafe for this form action.
