@redacto.io/consent-sdk-react 10.0.0-beta.9 → 10.0.0

package/src/RedactoPrivacyCenter/lib/sandbox.ts

@@ -1,104 +0,0 @@
-/**
- * Sandbox-mode singleton for the Privacy Center consent PoC.
- *
- * The Privacy Center resolves org/workspace/subject from the JWT into
- * sessionStorage and gates every fetch behind an OTP-refresh loop. Sandbox mode
- * bypasses all of that: a pasted static token plus an explicit test subject and
- * org/workspace. Because the Privacy Center is a single instance per page (the
- * same assumption the OTP refresh circuit breaker in `utils.ts` already makes),
- * the sandbox config lives in one module-level slot that `AuthProvider`
- * configures on mount and the fetch/auth layers read.
- *
- * When configured:
- *   - `syncJwtDataToSessionStorage` seeds sessionStorage from these fields
- *     instead of decoding the JWT,
- *   - `ensureValidToken` / `checkAndRefreshAuth` return the static token without
- *     ever calling `/otp/refresh`,
- *   - `privacyCenterApiFetch` sends the single `X-Consent-Token` header instead
- *     of `Authorization: Bearer` (its presence marks the request as
- *     `environment=test`). There is no subject header — the acting identity
- *     travels in the request's own payload: query params (`primary_email` /
- *     `primary_mobile`) on GET/query reads, and the body on POSTs. See
- *     `sandboxAuthHeaders` / `sandboxQueryIdentity` / `sandboxBodyIdentity` /
- *     `sandboxContact`.
- */
-
-import { SANDBOX_TOKEN_HEADER } from '../../shared/sandbox';
-import type { SandboxConfig, SandboxIdentityPayload } from './types';
-
-export { SANDBOX_TOKEN_HEADER };
-export type { SandboxConfig };
-
-let sandboxConfig: SandboxConfig | null = null;
-
-/**
- * Set (or clear, with `null`) the active sandbox configuration. Called by
- * `AuthProvider` when the sandbox token prop is present. Idempotent.
- */
-export const setSandboxConfig = (config: SandboxConfig | null): void => {
-  sandboxConfig = config;
-};
-
-/** The active sandbox config, or null when sandbox mode is off. */
-export const getSandboxConfig = (): SandboxConfig | null => sandboxConfig;
-
-/** True when the Privacy Center is running in sandbox mode. */
-export const isSandboxMode = (): boolean => sandboxConfig !== null;
-
-/**
- * Auth headers for a Privacy Center request in sandbox mode, or null when
- * sandbox mode is off (so the caller falls back to `Authorization: Bearer`).
- * Only the `X-Consent-Token` credential is sent; its presence marks the request
- * as `environment=test`. There is no subject header — the acting identity
- * travels in the request's own payload: query params on GET/query reads (see
- * {@link sandboxQueryIdentity}) and the body on POSTs (see
- * {@link sandboxBodyIdentity} / {@link sandboxContact}).
- */
-export const sandboxAuthHeaders = (): Record<string, string> | null => {
-  if (!sandboxConfig) {
-    return null;
-  }
-  return {
-    [SANDBOX_TOKEN_HEADER]: sandboxConfig.token,
-  };
-};
-
-/**
- * The identity payload fragment for the active sandbox acting principal:
- * `{ org_user_id }` when a UCIC is set (it takes precedence), else
- * `{ primary_email }` when the subject looks like an email (contains "@"),
- * otherwise `{ primary_mobile }`. Null when sandbox mode is off. Merge this into
- * a JSON request body (POST) so the server can resolve the acting test identity.
- */
-export const sandboxBodyIdentity = (): SandboxIdentityPayload | null => {
-  if (!sandboxConfig) {
-    return null;
-  }
-  if (sandboxConfig.ucic) {
-    return { org_user_id: sandboxConfig.ucic };
-  }
-  return sandboxConfig.subject.includes('@')
-    ? { primary_email: sandboxConfig.subject }
-    : { primary_mobile: sandboxConfig.subject };
-};
-
-/**
- * The identity query fragment for the active sandbox acting principal:
- * `{ org_user_id }` when a UCIC is set (it takes precedence), else
- * `{ primary_email }` when the subject looks like an email (contains "@"),
- * otherwise `{ primary_mobile }`. Null when sandbox mode is off. Append these to
- * a GET/query request's query string so the server can resolve the acting test
- * identity (it reads `org_user_id` / `primary_email` / `primary_mobile` query
- * params on sandbox reads).
- */
-export const sandboxQueryIdentity = (): SandboxIdentityPayload | null =>
-  sandboxBodyIdentity();
-
-/**
- * The raw sandbox contact string, for endpoints whose server field is a single
- * `contact` (the server classifies it as email/phone/UCIC) — create-case,
- * manage-consent. Prefers the UCIC over the email/mobile subject. Null when
- * sandbox mode is off.
- */
-export const sandboxContact = (): string | null =>
-  sandboxConfig ? sandboxConfig.ucic || sandboxConfig.subject : null;