[Bug] Misleading/Incompolete domain Bug
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- azure, python
调研方向
Start by tracing the device authorization response's verification_uri into the flow["message"] output; the issue says MSAL prints the server-provided URL as-is. Check the relevant device-flow code and tests to determine whether MSAL can safely handle the reported URL. Done means the device login guidance uses a working URL and the behavior is covered by a test.
由索引模型根据 Issue 内容生成。
描述
Misleading/Incompolete domain Bug
A typo returned by the login server while logging into azure using az cli. The CLI instructed me to use use-device-code to avoid getting login failure I was having, and the URL it provided was not not working. I had to guess to get the right domain to use in my browser: login.mircosoftonline.com rather worked
To Reproduce
Steps to reproduce the behavior:
log into Azure CLi using:
az login --use-device-code
# Output looked like this:
To sign in, use a web browser to open the page https://login.microsoft.com/device and enter the code ....
Expected behavior
I expected the URL provided by the CLI to work flawlessly and quick, which couldn't happen
What you see instead
The MSAL Python version
python -c "import msal; print(msal.__version__)"
% az version
{
"azure-cli": "2.90.0",
"azure-cli-core": "2.90.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {}
}
Additional context
After thorough huntinh, I found out that the device code message URL (https://login.microsoft.com/device) is not generated by Azure cli or msal python. It's returned directly by the Microsoft server as the verification_uri field in the device authorization response json. Both Azure CLI and msal just print it as-is (flow["message"])
- 主要语言
- Python
- 星标
- 971
- 派生
- 223
- 平均合并
- 13 小时 48 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AzureAD/microsoft-authentication-library-for-python 的其他 Issue
-
AzureSDK bug P1
难度 4/5 3-5 天 新手友好度 48/100
-
http_client docstring does not say that timeout, verify and proxies only configure the default session可能已有人在做 @HardMax71 于 38 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 25/100
-
[Bug] The built-in retry never retries the token POST: HTTPAdapter(max_retries=1) keeps urllib3's default allowed_methods可能已有人在做 @HardMax71 于 44 天前认领。 未关闭bug untriaged
难度 2/5 1-3 小时 新手友好度 35/100
AzureAD/microsoft-authentication-library-for-python#957 · 3 条评论 ·
-
public-client untriaged
难度 5/5 一周以上 新手友好度 25/100
-
[Bug] Interactive auth callback hangs forever when an idle connection reaches AuthCodeReceiver first可能已有人在做 @Thanatos9404 于 3 天前认领。 未关闭bug public-client
难度 4/5 1-2 天 新手友好度 48/100
AzureAD/microsoft-authentication-library-for-python#950 · 2 条评论 · 3 个 reaction ·
查看 AzureAD/microsoft-authentication-library-for-python 的全部 Issue
相似的 Issue
-
tunneld on Windows: Wi-Fi devices are not discovered because uvicorn runs on a ProactorEventLoop未关闭
难度 2/5 1-3 小时 新手友好度 76/100
doronz88/pymobiledevice3#2051 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
collabnix/awesome-mcp-lists#230 ·
维护者通常 9 天内回复
-
Groc schedules with out of range values pass config validation and fail later when the scheduler is built可能已有人在做 @auraseb 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
autowarefoundation/autoware_carla_scenario#342 ·
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 72/100
ianktoo/project-monitor#14 ·