Preflight checklist
Ory Network Project
No response
Describe your problem
When we try to use this field in our OAuth2Client resources, Kubernetes shows a warning:
"Warning: unknown field spec.accessTokenStrategy"
This prevents us from configuring JWT vs opaque token strategy at the client level.
Describe your ideal solution
Please include the accessTokenStrategy CRD field in the next hydra-maester Helm chart release (v0.61.0 or similar).
The field already exists here:
https://github.com/ory/k8s/blob/master/helm/charts/hydra-maester/crds/crd-oauth2clients.yaml
We just need it to be included in a tagged release so we can use it in production.
Workarounds or alternatives
Currently, we have to:
- Accept the warning messages
- Or remove the field and configure token strategy globally at the Hydra server level instead of per-client or via the API.
Neither option is ideal for our multi-tenant setup.
Version
0.60.1
Additional Context
No response
Preflight checklist
Ory Network Project
No response
Describe your problem
When we try to use this field in our OAuth2Client resources, Kubernetes shows a warning:
"Warning: unknown field spec.accessTokenStrategy"
This prevents us from configuring JWT vs opaque token strategy at the client level.
Describe your ideal solution
Please include the
accessTokenStrategyCRD field in the next hydra-maester Helm chart release (v0.61.0 or similar).The field already exists here:
https://github.com/ory/k8s/blob/master/helm/charts/hydra-maester/crds/crd-oauth2clients.yaml
We just need it to be included in a tagged release so we can use it in production.
Workarounds or alternatives
Currently, we have to:
Neither option is ideal for our multi-tenant setup.
Version
0.60.1
Additional Context
No response