Add User ID validation to ensure it is not an email or phone number #10102
+18
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
Add validation to exclude invalid
user_id(e.g. email or phone number) from Anthropic metadataRelevant issues
Fixes #10106
Type
🐛 Bug Fix
Changes
This PR introduces a validation check for the
user_idfield in the_litellm_metadatadictionary to ensure it does not contain personally identifiable information (PII) such as emails or phone numbers.Rationale
Anthropic requires that the
user_idin metadata must be a UUID, hash value, or other opaque, non-identifying identifier. It must not contain any personally identifiable information such as names, email addresses, or phone numbers. Including such data can lead to the API rejecting the request with a400 Bad Request error. ViewThis update ensures that if an invalid user_id is provided (e.g. an email), it will simply be excluded from the metadata, preventing avoidable request failures.