Fixed: createEmailAddress and updateEmailAddress accept blank email addresses (OFBIZ-13582) - #2002
Merged
mridulpathak merged 1 commit intoSep 15, 2026
Conversation
…ddresses (OFBIZ-13582) Both methods gated only on UtilValidate.isEmail(parameters.emailAddress), which returns true for a null or blank string by design. Combined with the servicedef declaring emailAddress required but with no type-validate rule, and the service engine's required-parameter check only rejecting null rather than blank, a caller passing an empty string sailed through and created or updated a real ContactMech with a blank infoString. The original minilang had two explicit checks, not-empty then format-valid, so both methods now reject a blank emailAddress before the format check runs.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Backported from trunk (#2001).