does anyone know if I could make basic auth work with oathkeeper, along the lines of

<https://x-auth-token>:JWT@my.oathkeeper/

?

Hey, check out our oahtkeeper examples here: https://github.com/ory/examples/tree/master/oathkeeper

i looked around, it doesn't seem to answer my question, but maybe for more context: I have a git-remote setup:

<https://oathkeeper/git-repo.git>

I am doing the following request:

git -c http.extraheader="Authorization: bearer XXX" push -v myremote main

So whenever I do this, git transforms this to the following URL:

<https://user:XXX@oathkeeper/git-repo.git>

This is similar to what github allows when clone/pushing with a PAT (personal access token). Now I can't figure out how I can configure oathkeeper to take the token from the URL (instead of a header). The config available is (`authn`pipeline):

bearer_token:
  token_from:

But that "only" allows for header, cookie or query_parameter. Maybe I am looking for the wrong method though. So any more advice?

Hmm not sure if you can use the URL here, tbh this goes beyond my Oathkeeper knowledge. Can you take a look maybe @worried-kitchen-94392

Hi there! To be honest, not 100% sure if we allow using fields directly from the url, maybe you can try using a mutator https://www.ory.sh/docs/oathkeeper/pipeline/mutator#header to extract the data to a header?

I‘ll trace it again but from what I can tell the extra header ends up in the URL, like basic auth. It sorta looks like the client_credential thing?