Andreas Würl

Same here. The error started after upgrading to Nextcloud 26. Using the `custom_oidc` login against Keycloak. ``` { "reqId": "QzkVxVQMgpgtkGpEheeJ", "level": 3, "time": "2023-03-23TXX:XX:XX+XX:00", "remoteAddr": "XXX.XXX.XX.XXX", "user": "--", "app": "index",...

Can confirm that. Applying the fix from https://github.com/nextcloud/server/pull/37192/commits/6881d2f2f15976514cc52d6ea49ff09c5bb81d2b helped.

I'm new to Rust and need to find out how to avoid lifetimes then. Should I prefer to use `String` instead of `&str` to achieve that?

The solution is now hopefully clean enough.

> On the other hand, there may exist multiple clients using this library, should the value reflect that or not? That would be a future update to enable overriding this...

We already have seen this here. This is expected to be an expensive fix, as we would have to fix the internals of the Jersey URI Builder. Unfortunately the opening...

Not sure if I understand your question correctly. If you have subresources, you have to give the full chain of resources so that the generator is able to create the...

Do you have an example of a case where this is wrong. Is it the case where a subresource method is not allowed and this is not considered here or...

So your path parameter `shop_id` should be also contained in the input and/or output schema objects of the endpoint as well? Then it is not only a path parameter, but...

Then lets better base this on an example or a failing test.