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, I opened an issue about a possible Hydra Maester bug with `scopeArray`: <https://github.com/ory/hydra-maester/issues/278>
I’m using `hydra-maester` `v0.0.41`. The `OAuth2Client` CRD accepts `scopeArray` and warns that `scope` is deprecated, but I found that deletion does not fully work when only `scopeArray` is set.
Observed behavior:
• `scopeArray` only: the Hydra client is created/updated correctly, has the expected `owner`, and the Kubernetes `OAuth2Client` has the finalizer.
• When deleting the Kubernetes `OAuth2Client`, the CR is removed, but the Hydra client remains.
• If I add deprecated `spec.scope`, deletion works correctly and the Hydra client is removed.
It looks like the delete/unregister path may still check `spec.scope` and return early when it is empty, without considering `spec.scopeArray`.
Does this look like a valid bug? I can try to open a PR if the expected fix is to make the delete path accept `scopeArray` as well.

<https://github.com/ory/hydra-maester/pull/279> :eyes: