mirror of https://github.com/saltbo/zpan.git synced 2026-09-19 10:01:12 +08:00

Files

T

saltboandClaude Opus 4.6 b817cab2c1 feat: ZPan v2.0 roadmap, architecture, and repo reset

Remove the Go v1 codebase (preserved in the v1 branch) and establish
the foundation for v2 — a complete rewrite in TypeScript (server) and
Rust (CLI/desktop). This commit includes the product roadmap (v2.0–v2.9),
technical architecture document, and updated project documentation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-30 20:57:15 -04:00

1.1 KiB

Raw Blame History

v2.3 — Auth & Access

Harden authentication with social login and OIDC. Give admins control over who can register.

Major Features

Authentication Enhancements

Social login (Google, GitHub, Discord, etc.)
OIDC support — connect any enterprise identity provider (Keycloak, Okta, Azure AD, Authing, etc.)
Login by username in addition to email
Email configuration (SMTP for password reset and notifications)

Registration Controls

Admin configurable: open registration / invite-code only / closed
Invite code system: generate single-use codes, track who used each code
Admin can generate invite codes in bulk

User Scenarios

Company with SSO:

Our team uses Okta. The admin configures OIDC in ZPan with our Okta discovery URL. Now everyone logs in with their company credentials.

Private instance:

I run ZPan for my friends. I set registration to invite-only, generate 10 codes, and hand them out. Each code works once.

v1 Issues Resolved

#173 OIDC login
#121 Registration gate
#120 Invite code system
#221 Login by nickname

1.1 KiB Raw Blame History