Self-hosted apps lack consistent support for centralized SSO
Self-hosting administrators want their apps to use an existing identity provider instead of maintaining separate accounts and login setups. But some apps lack OIDC or SAML support, while others have limited provider or group-mapping options, pushing teams toward per-app accounts and custom workarounds. A compatibility layer could help, though it would not solve every app’s authorization model or protocol-specific needs.
For self-hosting administrators and small platform teams. Mentioned from Nov 2019 to May 2026 on Bluesky, GitHub and Hacker News.
20 different people described this problem in 17 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 6.4/10
- Frequency
- 10.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
With a separate authentication service (including roles like admin) has already been set up, it's a pity when that can't be reused, duplicate accounts need to be created, and there's no longer one single place to manage who has access to what resources
This single sign on solution is useful for users that host several apps, and want to streamline and simplify user management and authentication across apps
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 19 more quotes from people who have this problem
- Current workarounds, existing solutions and risks