Option to disable access log for /.well-known/openid-configuration and /.well-known/jwks.json endpoints

[aarmam]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [X] This issue affects my Ory Network project.
• [X] I have joined the Ory Community Slack.
• [X] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

These endpoints are accessed frequently and generate considerable amount of logs.

Describe your ideal solution

Add similar option to disable these endpoints from access log

https://github.com/ory/hydra/blob/master/cmd/server/handler.go#L214-L216

Version

2.x

Additional Context

Will implement it if accepted!

[project0]

It would be great if there would be a capability to disable all access logs.

[aeneasr]

I don't think that we'll add per-endpoint logging, just because at some point the amount of config options explodes.

It would be great if there would be a capability to disable all access logs.

Disabling the logging for access is already possible by setting LOG_LEVEL=warn

[project0]

@aeneasr unfortunately this also disables all other info log messages.

[aeneasr]

True, out of all the options then it would probably be the best option to simply disable access logging all together?

[github-actions[bot]]

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 🙏✌️