Skip to content

Support unsetting jwks_uri from .well-known/openid-configuration endpoint #4029

Open

Description

@David-Wobrock

Preflight checklist

Ory Network Project

No response

Describe your problem

The well-known openid config endpoint always returns a jwks_uri key.
Some OAuth2 clients will fetch it.

However, when you only issue opaque tokens, and no id_token, it's unnecessary to have a jwks_uri specified.

Describe your ideal solution

A way to unset this key, or to make the value null.

There already is a jwks_url key in the Hydra config:

func (p *DefaultProvider) JWKSURL(ctx context.Context) *url.URL {
return p.getProvider(ctx).RequestURIF(KeyJWKSURL, urlx.AppendPaths(p.IssuerURL(ctx), "/.well-known/jwks.json"))
}

But if it's not a valid URL, it will fallback onto the issuer URL defined in our Hydra config.

Ideally, there would be a way to remove this key entirely.

Workarounds or alternatives

None found so far.

Version

2.3.0

Additional Context

No response

Activity

  1. github-actions commented on Sep 27, 2026

    @github-actions
    Contributor

    Hello contributors!

    I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

    • open a PR referencing and resolving the issue;
    • leave a comment on it and discuss ideas on how you could contribute towards resolving it;
    • leave a comment and describe in detail why this issue is critical for your use case;
    • open a new issue with updated details and a plan for resolving the issue.

    Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

    Unfortunately, burnout has become a topic of concern amongst open-source projects.

    It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

    The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

    If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

    Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

    Thank you 🙏✌️

  2. added
    staleFeedback from one or more authors is required to proceed.
    on Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    featNew feature or request.staleFeedback from one or more authors is required to proceed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions