[BUG] OAUTH_AUTO_REDIRECT works with forward auth but not from OIDC clients

[arthur-lai]

Describe the Bug

I noticed that I am no longer being automatically redirected to my OAUTH provider when arriving to Tinyauth through any services' normal OIDC flow, but NGINX auth_request triggers it successfully.

How to Reproduce

1. Set OAUTH_AUTO_REDIRECT=pocketid
2. Go to any app with OIDC integration after configuring it to use Tinyauth
3. Click on 'Log in with Open ID'
4. Tinyauth loads, but does not autoredirect to Pocket ID so I need to click the button manually

Expected Behavior

Show the "Oauth Auto Redirect" message and forward the user to Pocket ID

Additional Context

No response

Logs

No response

Operating System

Debian

Browser

Firefox and Chrome

Tinyauth Version

5.1.0

Docker Version (if applicable)

29.6.2

Human Written Confirmation

• I confirm this issue was written by me and not generated by an LLM or AI assistant.

[dosubot]

Hi @arthur-lai! I'm Dosu and I'm helping the Tinyauth team.

This looks like a legitimate bug. The root cause is that the OAuth auto-redirect logic is only implemented on the /login page [1], but the OIDC authorization flow redirects to a completely different page — /oidc/authorize [2] — which has no auto-redirect logic at all [3].

Why forward auth works: Nginx auth_request routes unauthenticated users to /login?redirect_uri=...&login_for=app [4], which hits the login page where auto-redirect is implemented.

Why OIDC doesn't: When an OIDC client initiates authorization, Tinyauth creates a server-side ticket and redirects to /oidc/authorize?login_for=oidc&oidc_ticket=... instead [5]. This page doesn't have the auto-redirect useEffect hook, and redirect_uri isn't even passed as a query parameter (it's stored in the ticket), so even if the logic were present, the required conditions wouldn't be met.

In short, the auto-redirect feature was built for the forward auth use case and was never extended to the OIDC consent page.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[anes300]

I'm experiencing the same issue.

[steveiliop56]

@arthur-lai @anes300 can you please test with v5.1.2-beta.3? It should have a fix for that.

[arthur-lai]

Looks like that did the trick! It's working on all of my services. Thank you for following up so quickly.