Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hi I'm wondering if it's possible to keep the path you are matching to in the upstream route ie. match = <http://127.0.0.1:4455/login>

I want to keep the /login on the upstream but it goes away in the browser after a GET request.  I'm new to oathkeeper so maybe I'm not using properly.

I believe if you match the “login” part of the path, it should keep the “login” bit in the upstream route.

I'm trying to use this on a SPA UI route if that adds more context.  I navigate to /login and it navigates upstream properly but the browser drops the /login on the redirect.

it was a problem with my app turns out. it works now