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

email_verified field type validation fails for some SAML users

未关闭
#789 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

首先,使用将 email_verified 值设置为非空字符串的方式,复现 issue 中描述的 client-info 获取过程,然后找到该字段的类型验证。完成的标准是:库接受 Auth0 值而不引发类型异常,并包含针对 SAML 情况的回归测试。

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

描述

bug
Checklist
  • I have looked into the Readme and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.
Description

Hello,

For SAML connections the work around to set the email verified to become true is to set it to a non-empty string (see https://community.auth0.com/t/set-email-verified-to-true-for-saml-based-enterprise-users/62650). The new library with type checking doesn't like this and throws a type exception when pulling data that includes email_verified

Reproduction
  1. Create a user in auth0 with email_verified set to a non-empty string
  2. In auth0 this is treated as "true"
  3. Pull this client info using the library
Additional context

No response

auth0-python version

5.1.0

Python version

3.13

主要语言
Python
星标
581
派生
189
平均合并
15 小时 33 分钟
30 天内合并 PR
6

贡献指南

打开贡献指南

从这里开始

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

auth0/auth0-python 的其他 Issue

查看 auth0/auth0-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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