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 Everyone, We are evaluating Keto (Ory in general) and we are facing an issue with the Keto gRPC api.
We always received this answer `Received RST_STREAM with code 2 triggered by internal client error: Protocol error` from postman or from our custom python implementation.
Do you have any advice or have you already faced this issue ? Could it be a Keto issue ?

I'd guess it is rather a problem on the network level

ensure that the traffic is not downgraded to HTTP1

where do you run Keto, what ingress do you use, ...

we are trying to access the version hosted in the cloud

ah ok I see, that one does not support grpc right now (because of ingress config issues)

using the host provide in the keto dashboard

but if we host a version in our k8s cluster the grpc service would be available right ?

do you have an estimation of the release date?

we aim for august, but cannot promise right now

Ok thank you very much again for your time and your answers