Skip to content

[Feature]: Move authentication configuration to database-backed settings #474

Description

@m43i

Problem Statement

Authentication behavior is currently configured primarily through environment variables. This limits operational flexibility because system administrators must coordinate deployment-level configuration changes instead of managing authentication settings directly from the application.

Proposed Solution

Add database-backed authentication settings that can be managed by authorized system administrators through the admin UI.

The implementation should include:

  • Persistent storage for authentication configuration.
  • Runtime loading of authentication settings from the database where appropriate.
  • Admin UI controls for supported authentication options.
  • Access control so only system administrators can view or modify these settings.
  • Secure handling of sensitive values such as credentials, secrets, and provider tokens.
  • Bootstrap behavior for first-time deployments before database settings exist.
  • Documentation updates describing the new configuration workflow.

Alternatives Considered

Continue using environment variables for all authentication configuration. This is simpler operationally for initial deployment, but it prevents authorized administrators from safely updating authentication behavior through the UI and requires infrastructure-level changes for routine configuration updates.

Additional Context

This is a feature request because it adds new administrative configuration capabilities rather than fixing broken behavior.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions