KitchenOwl app won't work with OIDC

[Diagonet]

I set up a VoidAuth OIDC app for KitchenOwl with the following redirect URL

https://kitchen.example.com/signin/redirect
kitchenowl:///signin/redirect

The example.com URL works, I can access it from the browser with no issues. I think the second one is for the app and it doesn't seem to work. When I try to log in from the app I get

{
  "timestamp": 1781557759486,
  "level": "error",
  "message": "oidc-provider authorization error",
  "details": {
    "response": {
      "statusCode": 400
    },
    "request": {
      "ip": "redacted",
      "method": "GET",
      "path": "/oidc/auth"
    }
  },
  "errors": [
    {
      "name": "InvalidRedirectUri",
      "message": "invalid_redirect_uri"
    }
  ]
}

EDIT: isn't there a way for voidauth to show the redirect URL that was used? I feel like that should be the default for the log message.
EDIT2: I am talking about the kitchenowl android app, that is the one that doesn't work.

[Diagonet]

if the redirect URL in the URL is correct seems that voidauth sees kitchenowl:/signin/redirect and the frontend won't allow to add that to the redirect URLs

[notquitenothing]

Yep it looks like the VoidAuth frontend is not happy that the mobile redirect URI for KitchenOwl doesn't have a hostname when parsed. It should not be required, I should be able to have a fix up for this shortly 😊

[Diagonet]

Would it be possible to have an env var to remove restrictions from the frontend for redirect URLs please?

[notquitenothing]

In the latest release the FE has been updated to accept redirect URLs like those required by KitchenOwl, let me know if it is working now!

[Diagonet]

Seems to be working now, thank you

[notquitenothing]

Nice! If you are inclined then it would of course be appreciated if you would add an entry for KitchenOwl to the OIDC App Guides documentation 🙂