Actions
Sub-Task #255
open
Epic #3: Implement a secure user authentication system
Feature #160: User Login
User Story #176: As a user, I want to log in via OAuth/OIDC, so that I can use existing providers
Backend: discovery endpoint for login page
Sub-Task #255:
Backend: discovery endpoint for login page
Start date:
09/01/2026
Due date:
% Done:
100%
Estimated time:
Description
Public endpoint listing the configured OIDC providers (id, name, icon/icon_url) so the login page can render one button per provider, driven by the config from the "OIDC provider configuration" subtask. No auth required to call it - it's used before the user is logged in.
Updated by
Actions
Depends on #254 's
Arc<dyn OidcProviderRegistry>(Domain port,libs/server/domain/src/oidc/ports/oidc_provider_registry.rs) for the list of enabled providers:provider_keys()+config(key)givesname,icon/icon_url, and the provider slug for building each login-start URL. The discovery endpoint response should expose onlykey,name,icon— neverclient_id/client_secret.Depends on #254's
Arc<dyn OidcProviderRegistry>(Domain port,libs/server/domain/src/oidc/ports/oidc_provider_registry.rs) for the list of enabled providers:provider_keys()+config(key)givesname,icon/icon_url, and the provider slug for building each login-start URL. The discovery endpoint response should expose onlykey,name,icon— neverclient_id/client_secret.