mirror of https://github.com/saltbo/zpan.git synced 2026-08-29 00:01:42 +08:00

Files

T

saltbo 8dcce94f7c docs: reorder roadmap — prioritize auth and teams over image bed

Move Auth & Access (social login, OIDC, invite codes) to v2.1 and Teams
to v2.2, shifting Sharing, Image Bed, and Branding to v2.3–v2.5. Remove
completed items (Drizzle migration, SVAR replacement) from Image Bed.

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

2026-04-12 09:49:31 -04:00

1.1 KiB

Raw Blame History

v2.1 — 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