Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

email_verified field type validation fails for some SAML users

Open
#789 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by reproducing the client-info pull described in the issue with an email_verified value set to a non-empty string, then locate the type validation for that field. Done means the library accepts the Auth0 value without raising a type exception and includes a regression test for the SAML case.

Written by the indexing model from the issue text.

Description

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

Dominant language
Python
Stars
581
Forks
189
Avg merge
15h 33m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from auth0/auth0-python

All issues in auth0/auth0-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.