🚀 Feature: proxy requests #491

New Issue

OVERLORD · 2025-10-07T00:16:53+03:00

OVERLORD commented

2025-10-07 00:16:53 +03:00

Originally created by @Shagon94 on GitHub.

Feature description

Allowing to proxy requests, for example for sites that don't support any form of authentication, or only support authentication based on a header.

Some examples include;

calibre-web - allows login via specific header that denotes username
radarr/sonarr/prowlarr - has basic auth
plain nginx - no auth at all

This feature is similar to authelia's proxy feature, where we essentially just require the user to authenticate before allowing login - https://www.authelia.com/integration/proxies/caddy/#basic-examples

Pitch

Allows for a much easier integration and support as most self-hosted tools have basic username+pass, or no authentication at all.

Originally created by @Shagon94 on GitHub. ### Feature description Allowing to proxy requests, for example for sites that don't support any form of authentication, or only support authentication based on a header. Some examples include; - calibre-web - allows login via specific header that denotes username - radarr/sonarr/prowlarr - has basic auth - plain nginx - no auth at all This feature is similar to authelia's proxy feature, where we essentially just require the user to authenticate before allowing login - https://www.authelia.com/integration/proxies/caddy/#basic-examples ### Pitch Allows for a much easier integration and support as most self-hosted tools have basic username+pass, or no authentication at all.

OVERLORD added the feature label 2025-10-07 00:16:53 +03:00

OVERLORD closed this issue

2025-10-07 00:16:54 +03:00

OVERLORD commented

2025-10-07 00:16:57 +03:00

@stonith404 commented on GitHub:

Thank you for your request. In my opinion this is beyond the scope of the project, as Pocket ID is designed solely to function as an OIDC provider. However, I’ve created a guide on how to proxy your services through Pocket ID using OAuth2 Proxy. Let me know if something is unclear in the guide :)

@stonith404 commented on GitHub: Thank you for your request. In my opinion this is beyond the scope of the project, as Pocket ID is designed solely to function as an OIDC provider. However, I’ve created a [guide](https://github.com/stonith404/pocket-id/blob/main/docs/proxy-services.md) on how to proxy your services through Pocket ID using [OAuth2 Proxy](https://oauth2-proxy.github.io/). Let me know if something is unclear in the guide :)

OVERLORD commented

2025-10-07 00:16:57 +03:00

@tajkirkpatrick commented on GitHub:

@stonith404 May you update the uptime-kuma guide (or assist me) with what the "callback url" in Pocket ID would be for a service that doesn't support oauth and you are using the oauth2-proxy container. I am having issues replicating the guide with a similar docker application.

@tajkirkpatrick commented on GitHub: @stonith404 May you update the uptime-kuma guide (or assist me) with what the "callback url" in Pocket ID would be for a service that doesn't support oauth and you are using the oauth2-proxy container. I am having issues replicating the guide with a similar docker application.

OVERLORD commented

2025-10-07 00:16:58 +03:00

@stonith404 commented on GitHub:

@tajkirkpatrick https://<uptima-kuma-domain>/oauth2/callback should work. I'll update the docs.

@stonith404 commented on GitHub: @tajkirkpatrick `https://<uptima-kuma-domain>/oauth2/callback` should work. I'll update the docs.

OVERLORD referenced this issue

2025-10-07 00:21:55 +03:00

[PR #491] [MERGED] chore(translations): update translations via Crowdin #760

OVERLORD referenced this issue

2025-10-07 00:21:59 +03:00

[PR #491] chore(translations): update translations via Crowdin #764

Sign in to join this conversation.