Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

OIDC auth flow gets stuck if auth request is triggered by subagent

未关闭
  • 哪里不对？
#7,182 7 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 5 天内回复

@surajksharma07 已经在做这个了。

开始于 2026年9月21日。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
authentication

调研方向

Start by tracing the OIDC auth request from a subagent tool call through the ADK API server and ADK Web UI, then compare it with the working root-agent path. Reproduce the flow described in the issue and verify that subagent-triggered requests resolve normally and that the Web UI displays the auth pop-up rather than only a manual code field.

由索引模型根据 Issue 内容生成。

描述

agent engine request clarification

🔴 Required Information

Please ensure all items in this section are completed to allow for efficient
triaging. Requests without complete information may be rejected / deprioritized.
If an item is not applicable to you - please mark it as N/A

Describe the Bug:
We are currently experiencing problems when using the recommended OIDC auth flow (via Keycloak) for toolsets. The issue arises of the auth request is triggered by a tool call associated to a subagent (and not the root agent). This affects both the ADK Web UI as well as the ADK API server. For the former, the auth pop-up never shows up in such a case (instead, only a text box to enter a code manually is shown). By contrast, if the auth request is triggered by a tool call associated to the root agent, everything works as expected. Also, the issue arises with the current version 2.9.1 of ADK, but has also been observed with the earlier version 2.8.0.

Steps to Reproduce:

  1. Set up a root agent with a subagent, where the latter has a tool requiring auth with an OIDC flow
  2. Prompt the agent to make the subagent issue a tool call, triggering the auth request
  3. Observe that the auth is never resolved; in case of the ADK Web UI, the corresponding pop-up is never triggered but only shows a text box to enter a code
  4. The logs make absolutely no notice of this event

Expected Behavior:
Subagents should be treated in an equivalent manner as root agents when it comes to auth requests, resolving the auth flow as expected.

Observed Behavior:
In the case the auth request is triggered by a subagent, the auth flow gets stuck and is never resolved. In case of the ADK Web UI, the corresponding pop-up is never triggered.

Environment Details:

  • ADK Library Version (pip show google-adk): 2.9.1 (but also observed with 2.8.0)
  • Desktop OS:** Ubuntu 24.04.5 LTS inside WSL on Windows 11
  • Python Version (python -V): 3.13.13

Model Information:

  • Are you using LiteLLM: No
  • Which model is being used: gemini-3.7-flash via Vertex AI

🟡 Optional Information

Providing this information greatly speeds up the resolution process.

Regression:
Tested and confirmed with both 2.8.0 and 2.9.1, no information available about earlier versions.

Logs:
As mentioned above, the logs make absolutely no notice of the stuck auth flow. They are entirely inconclusive.

Screenshots / Video:
N/A

Additional Context:
N/A

Minimal Reproduction Code:
N/A

How often has this issue occurred?:
The problem is 100% reproducible with the described flow.

主要语言
Python
星标
21.6k
派生
4k
平均合并
9 小时 59 分钟
30 天内合并 PR
5

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

google/adk-python 的其他 Issue

查看 google/adk-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。