How do I associate an agent created with a knowledge base associated with an apikey, and no apikey is automatically generated when the agent is created?

[YunXi24]

If the Ragflow v0.19.0 version is deployed locally, how does the intelligent assistant associated with the knowledge base uniquely identify the knowledge base, and does the apikey be the only API associated with a knowledge base?

[dosubot[bot]]

In Ragflow v0.19.0, agents (assistants) are associated with knowledge bases by specifying the knowledge base IDs (kb_ids) in the agent's DSL or workflow configuration—not by API key. No API key is automatically generated when you create an agent, and API keys are managed separately. API keys are used for authentication when accessing the REST API, but they do not bind agents to knowledge bases or vice versa.

A knowledge base is uniquely identified by its ID (kb_id), which you reference in the agent's configuration and API calls. The primary way to associate an agent with a knowledge base is by including the relevant kb_id in the agent's config, for example:

"retrieval:0": {
  "obj": {
    "component_name": "Retrieval",
    "params": {
      "kb_ids": ["your_kb_id_here"]
    }
  }
}

source

API keys are not the only way to associate with a knowledge base—they are an orthogonal security feature for API access, not for logical binding of agents and knowledge bases. The association is always via kb_id in the agent's configuration, and you can generate/manage API keys for API access as needed, but these are not tied to knowledge base creation or agent creation
(discussion, code).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[dosubot[bot]]

ragflow-xxx 开头的 apikey 和 /v1/conservation/list 接口需要的 Authorization token（像 IjgzZGMyZmJhNWIyMjEx... 这种格式）是两种完全不同的认证方式，不能互相转换，也没有接口可以用 ragflow-xxx apikey 换取 Authorization token。

/v1/conservation/list 需要的是登录/会话 token，你需要通过 /v1/user/login 接口，用邮箱和密码登录，返回的响应头里会有 Authorization 字段，把这个 token 用在后续接口请求的 Authorization 头里即可。这个 token 一般有效期一天，重新登录会生成新的 token，旧的会失效。参考1 参考2

ragflow-xxx apikey 主要用于部分需要 apikey 的接口，通常写成 Authorization: Bearer ragflow-xxx...，但 /v1/conservation/list 这类接口不支持用 apikey，只能用登录 token。参考

如果你需要获取登录 token，可以用如下方式（Python 示例）：

import requests

url = 'http://your-ragflow-address/v1/user/login'
data = {'email': '你的邮箱', 'password': '你的密码'}
resp = requests.post(url, json=data)
token = resp.headers['Authorization']

后续请求带上这个 token 即可：

Authorization: IjgzZGMyZmJhNWIyMjExZjBiOWUwMDI0MmFjMTEwMDA1Ig.aGuqWA.MlxijFGoPXx77bHmCx3H-eYAEU0

如有登录或 token 获取问题可以补充说明。

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[YunXi24]

哪个接口是通过知识库dialog_id生成对话的conversation_id的接口

[dosubot[bot]]

可以使用 POST /api/v1/chats/<dialog_id>/sessions 接口（其中 <dialog_id> 就是你的知识库/对话模板的 id）来生成 conversation_id（即新会话）。请求时需要在 header 里带上登录/会话 token（Authorization 字段），body 可以传 name 字段自定义会话名。

请求示例（假设 dialog_id 为 123456）：

curl -X POST http://your-ragflow-host/api/v1/chats/123456/sessions \
  -H "Authorization: <你的登录token>" \
  -H "Content-Type: application/json" \
  -d '{"name": "新会话"}'

返回结果会包含新生成的 conversation_id 及其它会话信息。
接口详情和参数见源码说明。

你也可以用 POST /api/v1/conversation/set，body 里传 dialog_id、is_new=true 也能新建会话，但推荐用上面那个接口，逻辑更清晰。

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[YunXi24]

Authorization的token多久会过期

[dosubot[bot]]

Ragflow 的登录/会话 Authorization token 官方文档和 issue 里说是“一天内过期”参考。但 Ragflow v0.19.0 的代码实际上没有自动失效机制，token 只要没被手动注销或删除，就会一直有效，不会自动过期。当前版本也没有配置项可以设置 token 有效期。如果需要让 token 失效，只能手动注销或删除。

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}