CaseMark tightens up its signup form
A small auth hotfix on kveton's fork hints at a bigger story about CaseMark running its own login stack.
The signup form on CaseMark's fork was telling users one thing while the backend enforced another. Password rules on the page didn't match what the server actually accepted, so anyone who slipped through the cracks got a generic failure instead of being told what was wrong. kveton landed a same-day fix that aligns the form's rules and copy with the real policy and pipes the backend's actual error messages through to the screen.
The more interesting signal is underneath. CaseMark is now running its own authentication layer - Better Auth, an open-source login toolkit - wired into a custom signup UI. That's a deliberate move away from leaning on a hosted identity provider, and it means small mismatches between the two halves become user-visible bugs the team has to chase.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?