Hi Kieron, sorry to hear that you are having troubles, you clearly come from a place of frustration. Please help me set some expectations: The slack community is not an official bug tracker, and it’s a place where developers help other developers.
I see that you have created 4 issues / and one discussions in Ory (
https://github.com/search?q=org%3Aory+author%3AKieronWiltshire&type=issues ), one of which is resolved and two of those are within the last 48 hours.
Ory’s engineering is less than 10 people, and we already have to support paying customers, fix bugs, advance the roadmap, keep the system alive, … - and we can’t offer real time support on Slack for free. We try to help people as best as we can, but it’s not a guarantee. Please also respect that we need to regenerate from a weeks of intense work on the weekend, and it can’t be the expectation that someone is helping during the downtime.
Regarding Oathkeeper, it’s a bit of Ory’s problem child. The reason for that is that we are not super happy how the system works and there are many rough edges. However, fixing that requires, in our mind, a complete refactor (or rewrite) of the product. That’s why we do not have Oathkeeper as the highest priority in development right now. I do agree though, that there is a need for such a product.
There is a clone of Oathkeeper that is improved a lot by dadrus, it’s this one:
https://github.com/dadrus/heimdall
Maybe this does what you need? Dadrus has been an active Ory contributor for some time.
I hope this helps understand expectations and limitations, but still provides a bit of help.