Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-2065

Email addresses with capital letters are incorrectly rejected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 2.2.2
    • 2.0.7
    • Core features

    • Standalone, on ubuntu 9.10, Java(TM) SE Runtime Environment (build 1.6.0_20-b02)

      Form validation says "The supplied email address is invalid." on page http://localhost:8095/crowd/console/secure/user/add, if email address contains capital letters. For example:

      "HELP@example.com" in the email field, fails with the error above.
      "help@example.com" however, works without error.

      Since both deliver to the same email address, the lowercase equivalent is the workaround for this bug.
      However, it can confuse users who may think that something is wrong in the mail configuration of crowd, rather than the form.

      An email address may contain upper-case letters as defined in RFC5322 (http://tools.ietf.org/html/rfc5322#section-3.4.1).
      including:

      Uppercase and lowercase English letters (a-z, A-Z)
      Digits 0 to 9
      Characters ! # $ % & ' * + - / = ? ^ _ `

      { | }

      ~
      Character .

            [CWD-2065] Email addresses with capital letters are incorrectly rejected

            AdrienA (Inactive) added a comment -

            It's fixed: now we only check the presence of @.
            The reason is: if we check against RFC-822 (1982), we may exclude some valid (but weird) syntax from RFC-2822; and there's no standard tool or regular expression to check against RFC-2822. All we want is to notify the user if he missed the field or put a name instead.

            AdrienA (Inactive) added a comment - It's fixed: now we only check the presence of @. The reason is: if we check against RFC-822 (1982), we may exclude some valid (but weird) syntax from RFC-2822; and there's no standard tool or regular expression to check against RFC-2822. All we want is to notify the user if he missed the field or put a name instead.

            David O'Flynn [Atlassian] added a comment -

            Is there any value in doing email validation at all? Maybe just validate that it doesn't contain any characters outside those specified by the RFC?

            David O'Flynn [Atlassian] added a comment - Is there any value in doing email validation at all? Maybe just validate that it doesn't contain any characters outside those specified by the RFC?

            Russell Martin [Atlassian] added a comment -

            Further, if the end character is lower case then there is no error.

            Example:

            "HELp@example.com" - no error
            "HeLP@example.com" - error

            Russell Martin [Atlassian] added a comment - Further, if the end character is lower case then there is no error. Example: "HELp@example.com" - no error "HeLP@example.com" - error

            joe added a comment -

            If we allow uppercase addresses through then it may cause confusion if people later try password recovery with a lowercase version.

            We could convert 'HELP@example.com' to lowercase immediately before adding. That would simplify things If someone tries to recover it as 'help@example.com'.

            joe added a comment - If we allow uppercase addresses through then it may cause confusion if people later try password recovery with a lowercase version. We could convert 'HELP@example.com' to lowercase immediately before adding. That would simplify things If someone tries to recover it as 'help@example.com'.

              aragot AdrienA (Inactive)
              ded38599e58d Andreas M. Antonopoulos
              Affected customers:
              2 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: