You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Support Basic Auth for "Home / Self-Hosted" Workloads #138
As a general observation, many at-home self-hosters find a lot of value in basic auth, avoiding the hassle of having to configure an enterprise-ready federated solution.
The current "dev credentials" option isn't intuitive for home users, especially inexperienced family members. They'll unintentionally end up logging in under the default dev profile, instead of their own credentials.
Proposed Solution
Provide a third option for authentication: profiles backed by basic authentication. This would bridge the gap between the unintuitive power-user "dev mode", and the enterprise-ready OIDC solution. This brings Wardrowbe into parity with many other "homelab" offerings, and increases accessibility and potentially, adoption rate.
Provide a toggle to allow power users to completely disable basic authentication and opt for the more secure OIDC option.
There was a reason to not use username password authentication. As a self-hoster myself I have alot of services running. It's nearly impossible to remember username and password so I use oidc or forward auth. Wardrowbe was built with similar mindset.
I will look into adding username and password auth if there is high demand.
There was a reason to not use username password authentication. As a self-hoster myself I have alot of services running. It's nearly impossible to remember username and password so I use oidc or forward auth. Wardrowbe was built with similar mindset.
I will look into adding username and password auth if there is high demand.
Thanks!
OIDC is awesome in an enterprise setting, but a hassle for my Homelab since I host so many services which have varying levels of support for modern authentication.
Activity
JannickNijholt commentedon Aug 17, 2026
I agree! Setting up PocketID, only for this application, feels like an overkill solution.
Anyesh commentedon Oct 12, 2026
There was a reason to not use username password authentication. As a self-hoster myself I have alot of services running. It's nearly impossible to remember username and password so I use oidc or forward auth. Wardrowbe was built with similar mindset.
I will look into adding username and password auth if there is high demand.
Thanks!
zkhcohen commentedon Oct 12, 2026
OIDC is awesome in an enterprise setting, but a hassle for my Homelab since I host so many services which have varying levels of support for modern authentication.
I just use a password manager for autofill.
I appreciate you taking a look!