Spike: Plan Phase 2 — Authentication for Kombu

[MessiasLima]

Description

Plan Phase 2 — Authentication for Kombu.

Background

Kombu needs to authenticate against both Umami Cloud (API key) and self-hosted instances (username / password), manage the current session, change the current user's password, and manage teams (create, join, delete).

Current Knowledge

• :umami-api already exposes Auth with login(username, password), login(apiKey), logout(), verify(); Me with getSession(), getTeams(), getWebsites(); and Teams with create, join, get, update, delete, members, and websites.
• No SDK gap issues are expected for this phase.
• Session persistence strategy should be decided in this spike.

Scope

• Confirm exact screens needed (Login, User preferences, Change password, Team list, Team create / join, Team detail / delete).
• Decide navigation structure and auth gate.
• Define the follow-up implementation tickets for the phase.

Out of scope: implementing the screens; server-side changes.

Outcomes

• List of concrete implementation tickets for Phase 2.
• Defined UI flow for Cloud vs Self-hosted login.
• Decision on session / token storage.
• Ticket titles and acceptance criteria ready for implementation.