@acarmisc/backstage-plugin-litellm-backend 0.16.0 → 0.17.0

package/dist/routes/bridge.js

@@ -17,6 +17,11 @@ function registerBridgeRoutes(router, ctx, bridgeOpts) {
     // own auth. Lets CLI clients list/mint virtual keys without holding the master
     // key. Gated by litellm.bridge.enabled; the verifier needs litellm.bridge.issuer.
     const bridgeCfg = (0, bridge_1.readBridgeConfig)(config);
+    // Same userIdDomain rule as the UI; the trusted email domains gate who may use the bridge.
+    const bridgeIdentity = {
+        userIdDomain,
+        trustedEmailDomains: bridgeCfg.allowedEmailDomains,
+    };
     let tokenVerifier = bridgeOpts.tokenVerifier;
     if (bridgeCfg.enabled && !tokenVerifier) {
         try {
@@ -63,7 +68,7 @@ function registerBridgeRoutes(router, ctx, bridgeOpts) {
         router.get('/bridge/keys', async (req, res) => {
             try {
                 const claims = await requireClaims(req);
-                const keys = await (0, bridge_1.bridgeListKeys)(client, claims, provisioningEnabled, provisioningDefaults, logger, userIdDomain);
+                const keys = await (0, bridge_1.bridgeListKeys)(client, claims, provisioningEnabled, provisioningDefaults, logger, bridgeIdentity);
                 res.json(keys);
             }
             catch (error) {
@@ -87,7 +92,7 @@ function registerBridgeRoutes(router, ctx, bridgeOpts) {
                 }
                 const input = parseResult.data;
                 // ── Resolve user identity from verified claims ───────────────────────
-                const userId = (0, bridge_1.resolveBridgeUserId)(claims, userIdDomain);
+                const userId = (0, bridge_1.resolveBridgeUserId)(claims, bridgeIdentity);
                 // ── Create key via unified service ──────────────────────────────────
                 const keyCreateCtx = {
                     client,

package/dist/routes/keys.js

@@ -343,15 +343,15 @@ function registerKeysRoutes(router, ctx) {
         try {
             const { keyId } = req.params;
             const { tokenEntityRef, key } = await authorizeKeyAction(req, keyId);
-            // Check if the key can be unblocked:
-            // - Owner can unblock a self-blocked key (metadata.blocked_by === tokenEntityRef)
-            // - Otherwise require the unblock permission
-            const isOwnerUnblockingOwnBlock = key.metadata?.blocked_by === tokenEntityRef;
-            if (!isOwnerUnblockingOwnBlock) {
-                if (!(await assertPermission(req, backstage_plugin_litellm_common_1.litellmKeyUnblockPermission))) {
-                    sendPermissionDenied(res, backstage_plugin_litellm_common_1.litellmKeyUnblockPermission);
-                    return;
-                }
+            // Unblocking always needs the dedicated permission, on top of ownership.
+            // `metadata.blocked_by` is deliberately NOT trusted here: it lives in a
+            // record the owner can influence (older keys, or a stale value left after
+            // an admin unblocked in the LiteLLM UI), so "I blocked it myself" can't be
+            // told apart from "an admin blocked it". Grant `litellm.key.unblock` only
+            // to roles that may lift blocks; everyone else asks an administrator.
+            if (!(await assertPermission(req, backstage_plugin_litellm_common_1.litellmKeyUnblockPermission))) {
+                sendPermissionDenied(res, backstage_plugin_litellm_common_1.litellmKeyUnblockPermission);
+                return;
             }
             await client.unblockKey(keyId);
             // Clear the block record on unblock. Set the fields to null rather than

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@acarmisc/backstage-plugin-litellm-backend",
-  "version": "0.16.0",
+  "version": "0.17.0",
   "description": "The Backstage backend plugin for LiteLLM governance",
   "backstage": {
     "role": "backend-plugin",