OIDC support

[maisatanel]

Hi! Love your app, I think it fills an important niche of a more lightweight and free shared knowledge base.

OIDC support would help complete the package so as to avoid excessive additional per-app configuration overhead. User data could be fetched from the profile claim automatically. Existing admin, viewer and editor roles could be mapped as OIDC claims for centralised RBAC.

Is OIDC support on the roadmap? What sort of things would need to be done before OIDC could be considered?

[maisatanel]

#609 TOTP could be handled by the external auth source instead of the app itself to reduce complexity.

[perber]

Hi @maisatanel,

Thanks for the kind words, and for the thoughtful suggestion.

I already have a few features planned for v0.10.0 and v0.11.0. After that, I’ll probably need to spend some time polishing the UI and improving the overall experience.

I agree that handling TOTP through an external auth provider would be a nice way to reduce complexity inside the app itself.

To be honest, OIDC is not currently on my roadmap, but I do think it would be a good addition. Before considering it properly, I’d want to look into a few things:

• how OIDC login would fit into the current authentication flow
• how user provisioning and profile syncing should work
• how existing roles like admin, editor, and viewer could be mapped from claims
• how to keep the setup simple for smaller/self-hosted deployments

I’ll keep this issue open for now so it can be discussed and tracked. Contributions or implementation ideas are welcome.