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 all :wave: Looking to implement a POC for login/registration flows in a React SPA using the client sdk. Some of the endpoints (such as <https://www.ory.sh/docs/reference/api#tag/frontend/operation/updateLoginFlow|updateLoginFlow>) are shown as experimental. Are there any reservations around using them, besides potential backwards compatibility issues? And is it accurate to say that I should be using the <https://github.com/ory/kratos-client-js|kratos-client> library instead of <https://github.com/ory/client-js|ory/client> when working with a self hosted version of Kratos? Thanks in advance!

I think there is no way around using these experimental endpoints, they are used to complete the flows and no alternative exists. I think the experimental is just there auch that they can change the endpoints in the future.

If you are self-hosting, it should be easy to keep frontend and backend in sync. It might just require some work when upgrading between versions.

Yes, kratos-client is the right choice for self-hosted setups. It is generated from the spec that the open source kratos implements (make sure to use the exact same version as your kratos version)

The ory client is almost the same, so it would also work in most cases. But because they are releasing ory/network more frequently than open source kratos, the two can diverge.