[GH-ISSUE #5428] Reverse Proxy Authentication: add support for Header and Basic/Digest auth methods #11178

Open
opened 2026-08-05 01:28:47 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @suhaibkn on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5428

Is your feature request related to a problem? Please describe.
Currently only 3 methods are available for reverse proxy use-cases: SSO, password, pin.
While these are all very good for web based use cases, they don't work very well for other use case (CI/CD, automation, homelab).

My specific use case is that I have a few services running on my homelab (nextcloud, audiobookshelf, ntfy) and I'd like to connect to them via their respective mobile apps without being connected to the tunnel. But I'd still like to make them inaccessible to the general web. I cannot use the currently supported 3 auth methods because the mobile clients don't support that, but I don't want to completely expose them to the public either.

Describe the solution you'd like
Add support for Header based auth and Basic/Digest auth methods. This way requests that don't match the headers tokens won't go through.

Additional context
BTW, Pangolin handles this. They support a basic auth like flow for Public resources. And a simple token (instead of auth header) can be generate by creating a resource link.

Originally created by @suhaibkn on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5428 **Is your feature request related to a problem? Please describe.** Currently only 3 methods are available for reverse proxy use-cases: SSO, password, pin. While these are all very good for web based use cases, they don't work very well for other use case (CI/CD, automation, homelab). My specific use case is that I have a few services running on my homelab (nextcloud, audiobookshelf, ntfy) and I'd like to connect to them via their respective mobile apps without being connected to the tunnel. But I'd still like to make them inaccessible to the general web. I cannot use the currently supported 3 auth methods because the mobile clients don't support that, but I don't want to completely expose them to the public either. **Describe the solution you'd like** Add support for Header based auth and Basic/Digest auth methods. This way requests that don't match the headers tokens won't go through. **Additional context** BTW, Pangolin handles this. They support a basic auth like flow for Public resources. And a simple token (instead of auth header) can be generate by creating a resource link.
saavagebueno added the feature-request label 2026-08-05 01:28:47 -04:00
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#11178