fix(connector): 接入代码生成默认带 X-API-Key

苏苏指出 3 个语言示例都没带 key, 复制到本地直接跑必然 401.

- 共享常量 `API_KEY = 'analyst-key-001'` (analyst 主体, L0~L2 + 受 marking 过滤).
- Python / JavaScript 示例: 注入 HEADERS (X-API-Key).
- WorkBuddy MCP 模板:
  * url 之前错填 `/api/v1/mcp/manifest` (只读清单), 改为 `/api/v1/mcp` (JSON-RPC 端点).
  * 加 `headers: { "X-API-Key": "..." }` 字段.
  * 注释明示是 JSON-RPC 2.0 Streamable HTTP + 失败排查命令.
- UI:
  * 默认 lang 从 py 改为 mcp (第一个显示 WorkBuddy, 苏苏要求).
  * 单选顺序调整 MCP 在前.
  * 顶部加 ⚠️ 提示"默认演示 key, 生产请替换".

测试:
- 带 key 调 /api/v1/connector/object-types → count=38 ✅
- 带 key POST /api/v1/mcp initialize → serverInfo=尚数网本体平台 ✅
- 复制配置进 ~/.workbuddy/mcp.json 后 WorkBuddy 可识别并信任该 MCP.
This commit is contained in:
admin committed 2026-08-08 17:09:21 +08:00
1 parent d0e3f6e4a9
commit aa8d4bf98e
1 file changed
+12 -6
+12 -6
View File
@@ -45,11 +45,13 @@
</div>
<div class="card">
<div class="sub">接入代码生成</div>
<div class="sub">接入代码生成
<span class="hint-mini">默认带演示 key <code>analyst-key-001</code>, 生产请在「访问控制 / 主体」新建后替换 ⚠️</span>
</div>
<el-radio-group v-model="lang" size="small">
<el-radio value="mcp">WorkBuddy MCP</el-radio>
<el-radio value="py">Python</el-radio>
<el-radio value="js">JavaScript</el-radio>
<el-radio value="mcp">WorkBuddy MCP</el-radio>
</el-radio-group>
<pre class="json">{{ codeSnippet }}</pre>
</div>
@@ -75,18 +77,22 @@ const q = ref({ type: '', expand: '' })
const filterText = ref('')
const loading = ref(false)
const queryResult = ref(null)
const lang = ref('py')
const lang = ref('mcp')
const baseURL = window.location.origin + '/api/v1'
// 默认演示 key (analyst 主体, 可读 L0~L2 + 受 marking 过滤). 生产请在「访问控制 / 主体」新建
// 专属 key 替换, 详见右上「执行日志」可观察主体活动.
const API_KEY = 'analyst-key-001'
const codeSnippet = computed(() => {
if (lang.value === 'py') {
return `import requests\nBASE = "${baseURL}/connector"\n# 列出全部对象类型\nr = requests.get(f"{BASE}/object-types")\nprint(r.json())\n# 图式查询:数据空间沿「包含」展开其数据产品\nr = requests.post(f"{BASE}/query", json={\n "type": "TrustedDataSpace",\n "filters": {}, "expand": "SpaceContainsProduct"\n})\nfor sp in r.json().get("neighbors", []):\n print(sp["type"], sp["pk"], sp["properties"])`
return `import requests\nBASE = "${baseURL}/connector"\nHEADERS = {"X-API-Key": "${API_KEY}"} # ⚠️ 默认演示 key, 请改为你的实际 key\n\n# 列出全部对象类型 (connector 接口走主体鉴权 + marking 过滤)\nr = requests.get(f"{BASE}/object-types", headers=HEADERS)\nr.raise_for_status()\nprint(r.json())\n\n# 图式查询: 数据空间沿「包含」展开其数据产品\nr = requests.post(f"{BASE}/query", json={\n "type": "TrustedDataSpace",\n "filters": {}, "expand": "SpaceContainsProduct"\n}, headers=HEADERS)\nr.raise_for_status()\nfor sp in r.json().get("neighbors", []):\n print(sp["type"], sp["pk"], sp["properties"])`
}
if (lang.value === 'js') {
return `const BASE = "${baseURL}/connector";\n// 列出全部对象类型\nconst types = await fetch(BASE + "/object-types").then(r => r.json());\n// 图式查询\nconst res = await fetch(BASE + "/query", {\n method: "POST", headers: { "Content-Type": "application/json" },\n body: JSON.stringify({ type: "TrustedDataSpace", expand: "SpaceContainsProduct" })\n}).then(r => r.json());\nconsole.log(res.neighbors);`
return `const BASE = "${baseURL}/connector";\nconst HEADERS = { "X-API-Key": "${API_KEY}" }; // ⚠️ 默认演示 key, 请改为你的实际 key\n\n// 列出全部对象类型 (connector 接口走主体鉴权 + marking 过滤)\nconst types = await fetch(BASE + "/object-types", { headers: HEADERS }).then(r => r.json());\n\n// 图式查询\nconst res = await fetch(BASE + "/query", {\n method: "POST",\n headers: { ...HEADERS, "Content-Type": "application/json" },\n body: JSON.stringify({ type: "TrustedDataSpace", expand: "SpaceContainsProduct" })\n}).then(r => r.json());\nconsole.log(res.neighbors);`
}
return `// WorkBuddy / 任意 MCP 客户端:直接调用 /mcp/manifest 获取工具定义\n// 以 HTTP 方式接入(示例为 MCP 代理配置):\n{\n "mcpServers": {\n "shangshu-ontology": {\n "type": "http",\n "url": "${window.location.origin}/api/v1/mcp/manifest"\n }\n }\n}\n// 工具列表见 /mcp/manifest 的 tools 字段,每个工具对应一个 connector 端点。`
// WorkBuddy MCP: JSON-RPC 2.0 Streamable HTTP 端点, 不是 manifest 端点
return `// WorkBuddy MCP 接入配置 (写入 ~/.workbuddy/mcp.json 后重启 WorkBuddy)\n//\n// 端点: ${baseURL}/mcp (JSON-RPC 2.0, 接受 Streamable HTTP)\n// 鉴权: X-API-Key 请求头, 默认演示 key 见下方, 生产请在「访问控制 / 主体」新建替换\n{\n "mcpServers": {\n "shangshu-ontology": {\n "type": "http",\n "url": "${baseURL}/mcp",\n "headers": {\n "X-API-Key": "${API_KEY}" // ⚠️ 默认演示 key (analyst), 请改为你的实际 key\n }\n }\n }\n}\n\n// 工具清单: GET ${baseURL}/mcp/manifest\n// 写入后到 WorkBuddy 自定义连接器页点「信任」即可启用.\n// 失败排查: 看 WorkBuddy 日志或本体容器 docker logs shangshu-ontology | grep -E "deny|allow".`
})
async function loadManifest() {