What problem does this solve?
Prismarr currently only supports a single local user. In homelab environments it's common to already have a central identity provider managing authentication for multiple self-hosted services.
Without OIDC support and multiple users, I either need to maintain a separate account for Prismarr or share a single account between users.
Describe the solution you'd like
Add support for generic OpenID Connect (OIDC) authentication and multiple users.
This would allow Prismarr to integrate with providers such as:
- Pocket ID
- Authentik
- Authelia
- Keycloak
Using a generic OIDC implementation would allow any standards-compliant identity provider to work without requiring provider-specific integrations.
Alternatives considered
Continuing to use a shared local account works, but it isn't ideal for user management, SSO, or MFA. Reverse proxy authentication is another option, but native OIDC support would provide a cleaner experience.
Additional context
I believe this fits Prismarr's scope, as it doesn't add media management functionality. It simply modernizes authentication and makes Prismarr easier to integrate into existing self-hosted environments.
Scope check
What problem does this solve?
Prismarr currently only supports a single local user. In homelab environments it's common to already have a central identity provider managing authentication for multiple self-hosted services.
Without OIDC support and multiple users, I either need to maintain a separate account for Prismarr or share a single account between users.
Describe the solution you'd like
Add support for generic OpenID Connect (OIDC) authentication and multiple users.
This would allow Prismarr to integrate with providers such as:
Using a generic OIDC implementation would allow any standards-compliant identity provider to work without requiring provider-specific integrations.
Alternatives considered
Continuing to use a shared local account works, but it isn't ideal for user management, SSO, or MFA. Reverse proxy authentication is another option, but native OIDC support would provide a cleaner experience.
Additional context
I believe this fits Prismarr's scope, as it doesn't add media management functionality. It simply modernizes authentication and makes Prismarr easier to integrate into existing self-hosted environments.
Scope check