Is there a way to debug against the actual URL that Oathkeep Ory Community #talk-oathkeeper

Is there a way to debug against the actual URL tha...

helpful-keyboard-62948

04/07/2022, 8:59 PM

Is there a way to debug against the actual URL that Oathkeeper sees when the decisions API is used programatically? Doesn't seem to be displayed anywhere in the logs, even with the log level set to

debug

damp-sunset-69236

04/08/2022, 6:33 AM

It usually shows this information in logs at the first request as far as I know. Do you need assistance to setup decision API? What technologies do you use?

helpful-keyboard-62948

04/08/2022, 2:56 PM

My issue was pointing my gateway at 4459 (proxy) rather than 4456 (api) and now I see the actual

path

being logged. I assumed because there was no
path
attached that the
Host
value it logs was just info about the server, but I see now that this is the actual URL it matches against +
path
which was not previously visible.

helpful-keyboard-62948

04/08/2022, 2:57 PM

This is k8's + Traefik so the Host naming convention was a little misleading to reason about at first

helpful-keyboard-62948

04/08/2022, 4:57 PM

After some trial and error with regex wildcards,

Host

in the logs is definitely not the URL it sees, seems to be something with the word

local

in it that isn't

localhost

or the FQDN you normally route between services with. Is the actual URL scheme that Oathkeeper gets through the decisions API not debuggable somewhere? EDIT: The URL it sees is the external host (what the end-user sees) once pointed to

:4456

, not the internal FQDN.

Open in Slack

Previous Next