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

So, one big change with hydra 2.0 is client ids are now generated by hydra. I have read and understood the rationale, but it creates a bit of a problem for us. We have a mobile client, and more than one server infrastructure. Currently, each infrastructure contain the same set of client ids, so clients keep track of this single client id, but can connect to any infrastructure. How are people handling this in hydra 2.0?

We’re considering to re-expose this capability to define IDs again. But it does come at performance cost …

<@U010F2N7G2X> :wave: I was wondering if there are any concrete plans yet to re-expose this capability or is this still unclear? Thank you.