Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi, just a quick question. If I do not want SSR, is there a possible way to safely handle/prevent csrf attacks sincec now csrf tokens can't be sent along with HTML?

Hi <@U05NL32RQ2F>

how are you rendering the UI? is it frontend only since you do not want server-side rendering?
The csrf token can still be set on the UI in a frontend only codebase (SPA) since the token is sent with the login/registration/verification/recovery/settings json payload. Ory uses a synchronizer token pattern which sets an additional csrf cookie in the browser. This is automatically set in fetch if you allow credentials.

<https://www.ory.sh/docs/kratos/concepts/security#defenses-against-cross-site-request-forgery>