🚀 Wiredoor now supports authentication with OAuth2 Proxy (Google, GitHub, Authentik, and more) #30
Replies: 3 comments 19 replies
-
|
Hi @dmesad , next question :D Is it possible to pass the See https://oauth2-proxy.github.io/oauth2-proxy/configuration/integration/ Best regards! |
Beta Was this translation helpful? Give feedback.
-
|
So I'm trying to set this up but I've realized you're really only limited to securing one subdomain using google as a provider. Is that correct? For example, I want to secure https://dashboard.myapp.com and https://info.myapp.com. In google, since I have to provide redirects back to the full domain name, this seems like it would require multiple Client ID and Secrets, where as Wiredoors configuration is only a singular entry. Any advice or tips would be appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
@dmesad I'm trying wiredoor, configured OIDC with PocketID all the proxied services work just fine but I can't seem to set OIDC for the wiredoor dashboard itself ... Is this possible? When I try to set OAuth for the dashboard it does not throw any errors but it just doesn't set it to it at all. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Wiredoor now includes full support for OAuth2 Proxy-based authentication.
That means you can now protect any exposed service behind a login screen using your favorite identity provider: Google, GitHub, Authentik, or any OIDC-compliant provider.
How it works
Just set the following environment variables in your
.env:You must register the Redirect URI like `https:///oauth2/callback in your provider's config.
➡️ Perfect for securing internal services like Home Assistant, Grafana, or any private dashboard.
Learn more:
Beta Was this translation helpful? Give feedback.
All reactions