Read-only admin endpoint to introspect configured OIDC providers

[humb1t]

Hellou there, I have a specific use case that, in my humble opinion, can be worth contributing to Kratos, yet I want to verify idea with maintainers firs and understand their position on that matter.

Context

I currently ship two artefacts that work around a gap in OSS Ory Kratos:

1. OryClient in my project calls Ory Network's Workspace API (GET /projects/{id} on api.console.ory.sh)
2. I use ory-project-mock - a static Caddy shim that responds to GET /projects/* with a hand-curated JSON fixture so local environment doesn't have to hit Ory Network, as I prefer to keep things separate from real environments.

The mock exists because OSS Kratos has the providers config loaded in memory but never exposes it via any API.

Research

I made a lookup for similar topics and found these issues/prs/discussions:

• ory/kratos#4154 - closed with "it is out of scope for this project to support an API for configuration." conclusion
• ory/kratos#3286 - draft PR for full OIDC-provider CRUD with 5 concrete objections (config-vs-DB precedence, hot-reload, circular deps, DB strain, multiple config sources)
• ory/kratos#3119 - earlier ask for the similar thing
• ory/kratos#4135 was clarified that "organizations are not open source ... we rely on making some features paid only."

Proposal

I would like to make a small contribution PR that will add READ-ONLY, HTTP API to get this information from OSS Kratos during the local env testing from configuration (NO NEW DATABASE ENTITIES).

P.S.

I know that my bet on this contribution is risky and there is 84% chance that it will be declined, yet I wasn't able to resist the desire to try my luck with it. In any case, I want to say thank you to Ory team 💜