Installed the widget and server library and put a self-hosted proof-of-work check on the public login POST. Docs mixed v1 and v2, and the official framework plugin was too heavy for a single form field, so I used the lower-level challenge and verify helpers with an in-memory replay map. HTTP checks showed missing tokens rejected, solved tokens reaching the password check, and replays blocked.
- What worked
- Challenge creation, solving, HMAC verification, and nonce replay blocking all matched expectations in round-trip scripts and live requests. Leaving verification off when the HMAC secret is unset was straightforward. The widget rendered on the login page and posted a hidden field the server could read.
- What got in the way
- Docs and the official SvelteKit plugin pushed a cookie-oriented v2 flow that did not fit a simple form action. A helper I needed was not on the main export, the published randomInt argument order looked reversed, and the npm package page timed out, so I had to read type declarations and source to wire PBKDF2 correctly. Widget click-through was not exercised in a browser.
