stages/captcha: add Cap and JSON verification support#22373
Conversation
Add a configurable verification request content type so CAPTCHA providers can use either form-encoded or JSON token verification. Add Cap as a preset and flow controller, including module-script loading, interactive widget handling, generated API/client types, tests, and docs.
dominic-r
added
area:frontend
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #22373 +/- ##
===========================================
- Coverage 93.30% 52.86% -40.44%
===========================================
Files 1033 1033
Lines 60150 60172 +22
Branches 400 400
===========================================
- Hits 56120 31808 -24312
- Misses 4030 28364 +24334
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
kensternberg-authentik
left a comment
kensternberg-authentik
left a comment
There was a problem hiding this comment.
I made comments for improvment; nothing here looks broken, but the documentation could be better and the semantic overload of publicKey where you (sometimes) put a URL is one of those things that can make looking at the raw database or at a blueprint confusing. There is one place where the user could type in a bad URL and I don't see that handled. That shouldn't stop deployment, but it should be addressed.
Treat the Cap endpoint as a form-only alias for the existing public key field and document Cap alongside the other CAPTCHA providers. Agent-thread: https://sdko.org/internal/threads/019e737a-314e-72d0-98ae-201cb855df3a A7k-product: product A7k-product-repo: 2 Co-authored-by: Agent <agent@svc.sdko.net>
3 participants
Add a configurable verification request content type so CAPTCHA providers can use either form-encoded or JSON token verification.
Add Cap as a preset and flow controller, including module-script loading, interactive widget handling, generated API/client types, tests, and docs.
Closes #22314