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

Hello <@U0522JVBD7H>
That is Ory CLI for Ory Network right?
Can you share a bit what the concern is to have it enabled - my thought is if you dont use it, should be fine?

So we would like to put controls around how changes are applied to the Ory Network. Ideally we want all changes to actually only go through source control via a PR which would then apply the changes to the network (possibly using the Ory CLI) but we don't want anyone manually using the CLI.

Is there a way to restrict access to the Ory CLI so that only a system process can use it or some specific identity.

We want to avoid giving access to the network via the portal as well, that would be a break glass procedure.

gotcha, that is a very reasonable use case.
let me look into it, if it is not on implemented/on the roadmap we should add it :slightly_smiling_face: