@oxyhq/core 5.0.0 → 5.1.0

package/dist/cjs/mixins/OxyServices.accounts.js

@@ -2,6 +2,8 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.OxyServicesAccountsMixin = OxyServicesAccountsMixin;
 const userIdentity_1 = require("../utils/userIdentity");
+const platform_1 = require("../utils/platform");
+const loggerUtils_1 = require("../utils/loggerUtils");
 const mixinHelpers_1 = require("./mixinHelpers");
 function OxyServicesAccountsMixin(Base) {
     return class extends Base {
@@ -57,10 +59,19 @@ function OxyServicesAccountsMixin(Base) {
          * Unlike the removed `X-Acting-As` delegation header, the returned session
          * IS the new identity: this plants `accessToken` as the active token —
          * exactly like `claimSessionByToken` / `verifyChallenge` — so every
-         * subsequent request authenticates as the target account. The refresh token
-         * is the server-set httpOnly `oxy_rt_<authuser>` cookie (never in the body),
-         * so it joins the device multi-account set and survives reload /
-         * `refresh-all` with no extra client work.
+         * subsequent request authenticates as the target account.
+         *
+         * Joining the device multi-account set (so the switch survives a reload and
+         * propagates cross-domain via `/auth/refresh-all`) requires a SECOND call, to
+         * `POST /auth/session`, made here after the token is planted. The switch route
+         * lives at `/accounts/*`, OUTSIDE the `oxy_rt_<authuser>` cookie's `Path=/auth`
+         * scope, so the server never sees the device's existing slots from it and
+         * would clobber slot 0 (destroying the operator's own session). `/auth/session`
+         * runs where those cookies ARE visible, so the server allocates a NEW slot that
+         * coexists with the operator's and returns its `authuser`. This step is
+         * web-only (native multi-account uses stored sessions, not cookies) and
+         * best-effort — a failure leaves the in-session switch intact; the switched
+         * account simply won't survive a reload until the cookie is next established.
          *
          * After planting, the SDK's identity-scoped GET cache is fully cleared so
          * every cached read re-fetches as the new account. (The consuming
@@ -77,11 +88,35 @@ function OxyServicesAccountsMixin(Base) {
                 const res = await this.makeRequest('POST', `/accounts/${encodeURIComponent(accountId)}/switch`, undefined, { cache: false });
                 // Plant the freshly minted session as the ACTIVE session, mirroring
                 // `claimSessionByToken` / `verifyChallenge`: the response body carries
-                // the first access token; the refresh token is the server-set httpOnly
-                // cookie, so there is nothing else to store here.
+                // the first access token. The device refresh cookie is established below.
                 if (res?.accessToken) {
                     this.setTokens(res.accessToken);
                 }
+                // Register the switched session in the device's multi-account set by
+                // establishing its first-party refresh cookie. This MUST be a separate
+                // call to `POST /auth/session`: the switch route is at `/accounts/*`,
+                // outside the `oxy_rt_<authuser>` cookie's `Path=/auth` scope, so it can
+                // never read the device's existing slots and would overwrite slot 0
+                // (destroying the operator's own session). `/auth/session` runs where the
+                // cookies ARE visible, so the server allocates a NEW slot that coexists
+                // with the operator's and returns its `authuser`. Web-only; best-effort.
+                let authuser = res.authuser;
+                if ((0, platform_1.isWeb)()) {
+                    try {
+                        const established = await this.makeRequest('POST', '/auth/session', undefined, { cache: false });
+                        if (typeof established?.authuser === 'number') {
+                            authuser = established.authuser;
+                        }
+                        // /auth/session mints a fresh access token off the same session;
+                        // re-plant it so the active token matches the rotated cookie.
+                        if (established?.accessToken) {
+                            this.setTokens(established.accessToken);
+                        }
+                    }
+                    catch (error) {
+                        loggerUtils_1.logger.warn('[OxyServices] Failed to establish device refresh cookie after account switch; the switch is active in-session but may not survive a reload', { component: 'OxyServices', method: 'switchToAccount' }, error);
+                    }
+                }
                 // Identity changed → drop the entire GET response cache so no entry
                 // personalised for the previous identity is reused. Cache keys are
                 // identity-scoped, so a different identity could not READ the old
@@ -90,6 +125,7 @@ function OxyServicesAccountsMixin(Base) {
                 this.clearCache();
                 return {
                     ...res,
+                    ...(typeof authuser === 'number' ? { authuser } : {}),
                     user: (0, userIdentity_1.normalizeUserIdentity)(res.user),
                 };
             }

package/dist/cjs/mixins/OxyServices.assets.js

@@ -2,6 +2,15 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.OxyServicesAssetsMixin = OxyServicesAssetsMixin;
 const protocol_1 = require("@oxyhq/protocol");
+const loggerUtils_1 = require("../utils/loggerUtils");
+const errorUtils_1 = require("../utils/errorUtils");
+/**
+ * Maximum number of ids sent per `POST /assets/service/by-ids` request. Matches
+ * the server-side batch cap (the route rejects empty or > 100 id arrays with a
+ * 400); larger inputs are split into multiple chunked calls and merged. Mirrors
+ * `getUsersByIds`'s `USERS_BY_IDS_CHUNK_SIZE`.
+ */
+const SERVICE_ASSET_METADATA_CHUNK_SIZE = 100;
 function OxyServicesAssetsMixin(Base) {
     return class extends Base {
         constructor(...args) {
@@ -147,6 +156,63 @@ function OxyServicesAssetsMixin(Base) {
             }
             return urls;
         }
+        /**
+         * Resolve many Oxy asset ids to their content-addressed metadata in one
+         * round-trip per chunk via `POST /assets/service/by-ids` (body `{ ids }`).
+         *
+         * Returns each asset's `sha256`, `mime`, byte `size`, and `status` — built
+         * for server-to-server callers (e.g. Mention's MTN Protocol blob-ref
+         * resolution) that need the content hash for an asset id. Ids are
+         * deduplicated and validated (empty/blank ids dropped) before being split
+         * into chunks of {@link SERVICE_ASSET_METADATA_CHUNK_SIZE} (the server-side
+         * cap). The server omits unknown/deleted ids from each chunk's `data`, so
+         * the merged result may be shorter than the requested id list and the caller
+         * is expected to map by `id`.
+         *
+         * **Service-token auth (required).** `/assets/service/by-ids` is guarded by
+         * `serviceAuthMiddleware` + the `files:read` scope and is called via
+         * `makeServiceRequest`, which attaches `Authorization: Bearer <serviceToken>`
+         * (the same client that calls `POST /assets/service/cache`). The calling
+         * client MUST be service-configured (`configureServiceAuth(apiKey,
+         * apiSecret)`) before invoking this method; otherwise `getServiceToken()`
+         * throws because no credentials are available. A plain user-session request
+         * is rejected by the route's service-auth guard.
+         *
+         * Resilience: chunks are independent. A failed chunk is logged and skipped —
+         * the method returns every entry that resolved successfully rather than
+         * discarding the whole call on one chunk's failure. An empty/whitespace-only
+         * input resolves immediately with `[]` and performs no network call.
+         *
+         * Not cached at the SDK layer: it's a POST keyed on a multi-id body (low hit
+         * rate), mirroring the sibling service/POST methods which never cache.
+         */
+        async getServiceAssetMetadataByIds(ids) {
+            const uniqueIds = Array.from(new Set(ids.filter((id) => typeof id === 'string' && id.trim().length > 0)));
+            if (uniqueIds.length === 0) {
+                return [];
+            }
+            const chunks = [];
+            for (let i = 0; i < uniqueIds.length; i += SERVICE_ASSET_METADATA_CHUNK_SIZE) {
+                chunks.push(uniqueIds.slice(i, i + SERVICE_ASSET_METADATA_CHUNK_SIZE));
+            }
+            // Run chunks concurrently; a single chunk failure must not sink the rest.
+            const settled = await Promise.all(chunks.map(async (chunk) => {
+                try {
+                    const entries = await this.makeServiceRequest('POST', '/assets/service/by-ids', { ids: chunk });
+                    return Array.isArray(entries) ? entries : [];
+                }
+                catch (error) {
+                    loggerUtils_1.logger.warn('getServiceAssetMetadataByIds: chunk failed, continuing with remaining chunks', {
+                        method: 'getServiceAssetMetadataByIds',
+                        chunkSize: chunk.length,
+                        status: (0, errorUtils_1.extractErrorStatus)(error),
+                        error: error instanceof Error ? error.message : String(error),
+                    });
+                    return [];
+                }
+            }));
+            return settled.flat();
+        }
         /**
          * Upload raw file data
          */