wire-mesh-core 1.9.0 → 1.10.0

package/dist/domain/tokens.cjs

@@ -214,6 +214,26 @@ async function verifyRevocationEntry(entry, options) {
 		claims
 	};
 }
+/** The narrowing arithmetic tokens.cddl's own delegation obligations require (bearer match, expiry within the parent's, scope narrows, same capability, delegations-remaining strictly less than the parent's) -- shared between mintCapabilityToken (which additionally builds and signs the resulting token) and canGrant (a pure query with no minting side effect at all), so the two can never silently drift into two different ideas of what "narrows" means. Returns the specific refusal reason, or undefined when every rule is satisfied. */
+function checkNarrowing(parentClaims, granterDeviceId, candidate) {
+	if (!bytesEqual(parentClaims.bearer, granterDeviceId)) return "parent_bearer_mismatch";
+	if (candidate.expires > parentClaims.expires) return "expires_exceeds_parent";
+	if (!scopeNarrows(parentClaims.scope, candidate.scope)) return "scope_does_not_narrow";
+	if (parentClaims.capability !== candidate.capability) return "capability_mismatch";
+	const parentRemaining = parentClaims["delegations-remaining"];
+	if (parentRemaining !== void 0 && (candidate.delegationsRemaining === void 0 || candidate.delegationsRemaining >= parentRemaining)) return "delegation_exceeds_parent";
+}
+/**
+* A pure query: could deviceId, presenting heldToken as its own delegation authority, successfully mint a delegation matching candidate right now -- without attempting (and potentially failing) a real mint just to find out. Reuses mintCapabilityToken's own narrowing arithmetic via checkNarrowing, so the two can never silently drift into different ideas of what "narrows" means.
+*
+* Deliberately narrower than a full mint attempt in one respect: this checks only the narrowing rules tokens.cddl's own delegation obligations require (bearer match, expiry, scope, capability, delegations-remaining), the same scope mintCapabilityToken itself checks a *parent* against -- it does not verify heldToken's own signature or revocation status, exactly as mintCapabilityToken never re-verifies its own parent's signature either. A caller that also needs heldToken's cryptographic validity confirmed calls verifyCapabilityToken separately.
+*/
+function canGrant(heldToken, deviceId, candidate, now) {
+	if (candidate.expires <= now) return false;
+	const heldClaims = decodeTokenClaims(heldToken);
+	if (heldClaims === void 0) return false;
+	return checkNarrowing(heldClaims, deviceId, candidate) === void 0;
+}
 /**
 * Mints one capability token: builds token-claims from the given fields, signs it as a COSE_Sign1 under `identity`'s own key, with a protected header matching what the frozen conformance vectors actually encode (`{1: alg, 4: issuer device-id}`, not the empty header a token merely needs to verify against itself).
 *
@@ -231,26 +251,15 @@ async function mintCapabilityToken(options) {
 			ok: false,
 			reason: "parent_malformed"
 		};
-		if (!bytesEqual(parentClaims.bearer, options.identity.deviceId)) return {
-			ok: false,
-			reason: "parent_bearer_mismatch"
-		};
-		if (options.expires > parentClaims.expires) return {
+		const refusal = checkNarrowing(parentClaims, options.identity.deviceId, {
+			capability: options.capability,
+			scope: options.scope,
+			expires: options.expires,
+			...options.delegationsRemaining !== void 0 ? { delegationsRemaining: options.delegationsRemaining } : {}
+		});
+		if (refusal !== void 0) return {
 			ok: false,
-			reason: "expires_exceeds_parent"
-		};
-		if (!scopeNarrows(parentClaims.scope, options.scope)) return {
-			ok: false,
-			reason: "scope_does_not_narrow"
-		};
-		if (parentClaims.capability !== options.capability) return {
-			ok: false,
-			reason: "capability_mismatch"
-		};
-		const parentRemaining = parentClaims["delegations-remaining"];
-		if (parentRemaining !== void 0 && (options.delegationsRemaining === void 0 || options.delegationsRemaining >= parentRemaining)) return {
-			ok: false,
-			reason: "delegation_exceeds_parent"
+			reason: refusal
 		};
 		parentBytes = encodeBuf(options.parent);
 	}
@@ -294,6 +303,7 @@ async function mintRevocationEntry(options) {
 	];
 }
 //#endregion
+exports.canGrant = canGrant;
 exports.mintCapabilityToken = mintCapabilityToken;
 exports.mintRevocationEntry = mintRevocationEntry;
 exports.verifyCapabilityToken = verifyCapabilityToken;

package/dist/domain/tokens.d.cts

@@ -55,6 +55,19 @@ export type MintVerdict = {
   ok: false;
   reason: MintRefusalReason;
 };
+/** What a would-be delegation needs, to check it narrows a specific parent -- everything mintCapabilityToken itself checks a delegation against, independent of the tokenId/bearer/notBefore/signing concerns unique to actually minting one. */
+interface NarrowingCandidate {
+  capability: TokenClaims["capability"];
+  scope: TokenClaims["scope"];
+  expires: number;
+  delegationsRemaining?: number;
+}
+/**
+ * A pure query: could deviceId, presenting heldToken as its own delegation authority, successfully mint a delegation matching candidate right now -- without attempting (and potentially failing) a real mint just to find out. Reuses mintCapabilityToken's own narrowing arithmetic via checkNarrowing, so the two can never silently drift into different ideas of what "narrows" means.
+ *
+ * Deliberately narrower than a full mint attempt in one respect: this checks only the narrowing rules tokens.cddl's own delegation obligations require (bearer match, expiry, scope, capability, delegations-remaining), the same scope mintCapabilityToken itself checks a *parent* against -- it does not verify heldToken's own signature or revocation status, exactly as mintCapabilityToken never re-verifies its own parent's signature either. A caller that also needs heldToken's cryptographic validity confirmed calls verifyCapabilityToken separately.
+ */
+export declare function canGrant(heldToken: CapabilityToken, deviceId: DeviceId, candidate: Readonly<NarrowingCandidate>, now: number): boolean;
 export interface MintCapabilityTokenOptions {
   /** The issuer -- signs the token, and supplies the self-certifying issuer/issuer-key claims. */
   identity: IdentityPort;

package/dist/domain/tokens.d.mts

@@ -55,6 +55,19 @@ export type MintVerdict = {
   ok: false;
   reason: MintRefusalReason;
 };
+/** What a would-be delegation needs, to check it narrows a specific parent -- everything mintCapabilityToken itself checks a delegation against, independent of the tokenId/bearer/notBefore/signing concerns unique to actually minting one. */
+interface NarrowingCandidate {
+  capability: TokenClaims["capability"];
+  scope: TokenClaims["scope"];
+  expires: number;
+  delegationsRemaining?: number;
+}
+/**
+ * A pure query: could deviceId, presenting heldToken as its own delegation authority, successfully mint a delegation matching candidate right now -- without attempting (and potentially failing) a real mint just to find out. Reuses mintCapabilityToken's own narrowing arithmetic via checkNarrowing, so the two can never silently drift into different ideas of what "narrows" means.
+ *
+ * Deliberately narrower than a full mint attempt in one respect: this checks only the narrowing rules tokens.cddl's own delegation obligations require (bearer match, expiry, scope, capability, delegations-remaining), the same scope mintCapabilityToken itself checks a *parent* against -- it does not verify heldToken's own signature or revocation status, exactly as mintCapabilityToken never re-verifies its own parent's signature either. A caller that also needs heldToken's cryptographic validity confirmed calls verifyCapabilityToken separately.
+ */
+export declare function canGrant(heldToken: CapabilityToken, deviceId: DeviceId, candidate: Readonly<NarrowingCandidate>, now: number): boolean;
 export interface MintCapabilityTokenOptions {
   /** The issuer -- signs the token, and supplies the self-certifying issuer/issuer-key claims. */
   identity: IdentityPort;

package/dist/domain/tokens.mjs

@@ -213,6 +213,26 @@ async function verifyRevocationEntry(entry, options) {
 		claims
 	};
 }
+/** The narrowing arithmetic tokens.cddl's own delegation obligations require (bearer match, expiry within the parent's, scope narrows, same capability, delegations-remaining strictly less than the parent's) -- shared between mintCapabilityToken (which additionally builds and signs the resulting token) and canGrant (a pure query with no minting side effect at all), so the two can never silently drift into two different ideas of what "narrows" means. Returns the specific refusal reason, or undefined when every rule is satisfied. */
+function checkNarrowing(parentClaims, granterDeviceId, candidate) {
+	if (!bytesEqual(parentClaims.bearer, granterDeviceId)) return "parent_bearer_mismatch";
+	if (candidate.expires > parentClaims.expires) return "expires_exceeds_parent";
+	if (!scopeNarrows(parentClaims.scope, candidate.scope)) return "scope_does_not_narrow";
+	if (parentClaims.capability !== candidate.capability) return "capability_mismatch";
+	const parentRemaining = parentClaims["delegations-remaining"];
+	if (parentRemaining !== void 0 && (candidate.delegationsRemaining === void 0 || candidate.delegationsRemaining >= parentRemaining)) return "delegation_exceeds_parent";
+}
+/**
+* A pure query: could deviceId, presenting heldToken as its own delegation authority, successfully mint a delegation matching candidate right now -- without attempting (and potentially failing) a real mint just to find out. Reuses mintCapabilityToken's own narrowing arithmetic via checkNarrowing, so the two can never silently drift into different ideas of what "narrows" means.
+*
+* Deliberately narrower than a full mint attempt in one respect: this checks only the narrowing rules tokens.cddl's own delegation obligations require (bearer match, expiry, scope, capability, delegations-remaining), the same scope mintCapabilityToken itself checks a *parent* against -- it does not verify heldToken's own signature or revocation status, exactly as mintCapabilityToken never re-verifies its own parent's signature either. A caller that also needs heldToken's cryptographic validity confirmed calls verifyCapabilityToken separately.
+*/
+function canGrant(heldToken, deviceId, candidate, now) {
+	if (candidate.expires <= now) return false;
+	const heldClaims = decodeTokenClaims(heldToken);
+	if (heldClaims === void 0) return false;
+	return checkNarrowing(heldClaims, deviceId, candidate) === void 0;
+}
 /**
 * Mints one capability token: builds token-claims from the given fields, signs it as a COSE_Sign1 under `identity`'s own key, with a protected header matching what the frozen conformance vectors actually encode (`{1: alg, 4: issuer device-id}`, not the empty header a token merely needs to verify against itself).
 *
@@ -230,26 +250,15 @@ async function mintCapabilityToken(options) {
 			ok: false,
 			reason: "parent_malformed"
 		};
-		if (!bytesEqual(parentClaims.bearer, options.identity.deviceId)) return {
-			ok: false,
-			reason: "parent_bearer_mismatch"
-		};
-		if (options.expires > parentClaims.expires) return {
+		const refusal = checkNarrowing(parentClaims, options.identity.deviceId, {
+			capability: options.capability,
+			scope: options.scope,
+			expires: options.expires,
+			...options.delegationsRemaining !== void 0 ? { delegationsRemaining: options.delegationsRemaining } : {}
+		});
+		if (refusal !== void 0) return {
 			ok: false,
-			reason: "expires_exceeds_parent"
-		};
-		if (!scopeNarrows(parentClaims.scope, options.scope)) return {
-			ok: false,
-			reason: "scope_does_not_narrow"
-		};
-		if (parentClaims.capability !== options.capability) return {
-			ok: false,
-			reason: "capability_mismatch"
-		};
-		const parentRemaining = parentClaims["delegations-remaining"];
-		if (parentRemaining !== void 0 && (options.delegationsRemaining === void 0 || options.delegationsRemaining >= parentRemaining)) return {
-			ok: false,
-			reason: "delegation_exceeds_parent"
+			reason: refusal
 		};
 		parentBytes = encodeBuf(options.parent);
 	}
@@ -293,4 +302,4 @@ async function mintRevocationEntry(options) {
 	];
 }
 //#endregion
-export { mintCapabilityToken, mintRevocationEntry, verifyCapabilityToken, verifyRevocationEntry };
+export { canGrant, mintCapabilityToken, mintRevocationEntry, verifyCapabilityToken, verifyRevocationEntry };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wire-mesh-core",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "type": "module",
   "packageManager": "pnpm@10.33.0",
   "repository": {