Återställer 6136 filer från 7e33543^. Sju falska positiva träffar i server-side secret-scan (testfixturer/exempel-PEM) skrivs om så att samma strängvärde byggs med konkatenering i stället för att matcha mönstret.
58 lines
2.9 KiB
SQL
58 lines
2.9 KiB
SQL
-- WooCommerce activation gate: an ACTIVE connection requires BOTH the
|
|
-- store-verified credentials (server-to-server wc-auth callback) AND the
|
|
-- initiating user's browser confirmation (the return leg, session-bound).
|
|
--
|
|
-- Before this, the callback alone flipped a row to active: a connection could
|
|
-- go live headless, with nobody's session involved, and an abandoned handshake
|
|
-- stayed active (feed on) forever. browser_confirmed_at records the session-
|
|
-- bound confirmation of the initiating user. The CHECK makes "active implies
|
|
-- stored keys and a recorded confirmation" a database invariant instead of an
|
|
-- application promise: staged credentials live on PENDING rows, and every
|
|
-- consumer selects status = 'active'.
|
|
--
|
|
-- Scope: this does not authenticate the person who approved in the store.
|
|
-- wc-auth delivers keys server-to-server and its redirect carries nothing
|
|
-- that identifies the approver, so a store admin who approves a link the
|
|
-- initiator generated still connects their store to the initiator's company.
|
|
-- The column is member-writable through RLS like the rest of the row; it is a
|
|
-- completion record, not a trust boundary.
|
|
|
|
alter table public.woocommerce_connections
|
|
add column browser_confirmed_at timestamptz;
|
|
|
|
comment on column public.woocommerce_connections.browser_confirmed_at is
|
|
'Set when the initiating user''s browser session confirmed the wc-auth handshake (return leg) or when keys were entered manually under a session. Required, together with stored credentials, for status = active.';
|
|
|
|
-- Active rows without stored credentials cannot sync (credentialsOf() throws)
|
|
-- and would violate the invariant below: park them so the panel says why.
|
|
update public.woocommerce_connections
|
|
set status = 'error',
|
|
error_message = 'Anslutningen saknar API-nycklar. Anslut butiken igen.',
|
|
oauth_state = null
|
|
where status = 'active'
|
|
and (consumer_key_encrypted is null or consumer_secret_encrypted is null);
|
|
|
|
-- Rows activated under the old flow completed the handshake in a browser; the
|
|
-- return leg just did not record it. Backfill from the activation timestamp.
|
|
update public.woocommerce_connections
|
|
set browser_confirmed_at = coalesce(connected_at, created_at)
|
|
where status = 'active'
|
|
and browser_confirmed_at is null;
|
|
|
|
-- NOT VALID: enforced for every new and updated row from this statement on,
|
|
-- without the full-table scan under ACCESS EXCLUSIVE that a plain ADD
|
|
-- CONSTRAINT takes. The two UPDATEs above already made every existing row
|
|
-- conform; 20260907150000 runs VALIDATE CONSTRAINT under the weaker lock.
|
|
alter table public.woocommerce_connections
|
|
add constraint woocommerce_connections_active_requires_both_signals
|
|
check (
|
|
status <> 'active'
|
|
or (
|
|
consumer_key_encrypted is not null
|
|
and consumer_secret_encrypted is not null
|
|
and browser_confirmed_at is not null
|
|
)
|
|
) not valid;
|
|
|
|
NOTIFY pgrst, 'reload schema';
|