3611a8607d
* feat(rbac): add multi-use share-link invitations for invite_only mode When the auth.registration_mode toggle flips to invite_only, the public /auth/register endpoint returns 403 — but until now there was no channel for unregistered users to actually join a tenant. The existing invitation table required a registered invitee, so new emails could not enter the system at all. This change introduces a share-link model: - Owner generates a multi-use registration link with a per-tenant role - Recipient opens the link, registers with their own email, and is added to the tenant on the same request - Token is stored in plaintext (not hashed) so the management UI can re-display the URL on demand without a "copy now or revoke" trap. Threat model is bounded by 7-day TTL, revocability, and the fact that all the link grants is membership in one tenant. - accepted_count tracks how many users joined through the link so the Owner can tell whether a link is fresh or has already been spread Per-user invitations (registered email -> in-app inbox accept) are unchanged. Share-link rows use empty invitee_user_id as discriminator; the partial unique index on (tenant_id, invitee_user_id) was relaxed to skip empty values so multiple share links can coexist per tenant. Frontend reuses Login.vue for /register?token=xxx instead of a parallel page, and adds icon-only revoke / remove actions plus a distinct "active" status tag for share-link rows. Migration 000054 adds the token column, the accepted_count column, and the relaxed pending unique index in a single step. * feat(auth): update invitation token handling and add rate limiting - Refactor the invitation token retrieval to use POST instead of GET, enhancing security by preventing the plaintext token from appearing in logs and browser history. - Update the API endpoint from `/auth/invitations/:token` to `/auth/invitations/lookup` to reflect the new method. - Introduce a rate limiter for unauthenticated share-link endpoints to mitigate brute-force attacks and abuse, ensuring a maximum of 30 requests per minute per IP. - Adjust the registration flow to maintain user experience while securing the invitation process.
49 lines
2.4 KiB
SQL
49 lines
2.4 KiB
SQL
-- Migration: 000054_invitation_share_links
|
|
-- Extends tenant_invitations with the columns needed for "share link"
|
|
-- invitations: a multi-use registration link an Owner can drop in a
|
|
-- group chat. The existing per-user invitation flow (rows with a real
|
|
-- invitee_user_id) keeps working unchanged.
|
|
--
|
|
-- Schema changes:
|
|
-- * invitee_user_id is given a default empty string. Share-link rows
|
|
-- start with no specific invitee — whoever holds the link
|
|
-- registers themselves with their own email. Per-user invitations
|
|
-- still write the resolved user id at create-time.
|
|
-- * token holds the plaintext registration token for share-link
|
|
-- rows. We store plaintext (not a hash) deliberately: the threat
|
|
-- model is bounded by short TTL, revocability, and the fact that
|
|
-- consuming the link only grants membership in one tenant.
|
|
-- Plaintext lets the management UI re-display the link on demand
|
|
-- so the Owner doesn't have to "copy now or revoke and re-issue".
|
|
-- * accepted_count counts how many users have completed registration
|
|
-- through the row. Per-user invitations cap at 1 and flip to
|
|
-- accepted in the same step; share-link rows accumulate — surfaced
|
|
-- in the management UI as "N 人已加入" so Owners can tell whether
|
|
-- a link is fresh or has already been used widely.
|
|
--
|
|
-- Index changes:
|
|
-- * The pending-uniqueness index on (tenant_id, invitee_user_id) is
|
|
-- relaxed to skip empty values so multiple share-link rows can
|
|
-- coexist on the same tenant.
|
|
-- * token gets its own partial unique index for lookup at
|
|
-- /auth/register-by-invite.
|
|
DO $$ BEGIN RAISE NOTICE '[Migration 000054] Extending tenant_invitations for share-link invitations'; END $$;
|
|
|
|
ALTER TABLE tenant_invitations
|
|
ALTER COLUMN invitee_user_id SET DEFAULT '',
|
|
ADD COLUMN IF NOT EXISTS token VARCHAR(64) NOT NULL DEFAULT '',
|
|
ADD COLUMN IF NOT EXISTS accepted_count INTEGER NOT NULL DEFAULT 0;
|
|
|
|
DROP INDEX IF EXISTS idx_tenant_invitations_unique_pending;
|
|
CREATE UNIQUE INDEX IF NOT EXISTS idx_tenant_invitations_unique_pending
|
|
ON tenant_invitations(tenant_id, invitee_user_id)
|
|
WHERE status = 'pending'
|
|
AND deleted_at IS NULL
|
|
AND invitee_user_id <> '';
|
|
|
|
CREATE UNIQUE INDEX IF NOT EXISTS idx_tenant_invitations_token
|
|
ON tenant_invitations(token)
|
|
WHERE token <> '' AND deleted_at IS NULL;
|
|
|
|
DO $$ BEGIN RAISE NOTICE '[Migration 000054] tenant_invitations extended'; END $$;
|