Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-8764

No error message when creating a tenant with org name that is too long

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • 2.12.0 GA
    • System
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide

      1. in the master portal, go to Accounts > Create
      2. Enter all fields correctly, and set the maximum size for the Org Name field (255 chars)
      3. Click Create Account

      Actual behavior:
      The page gets reloaded and no error message is shown.

      Expected behavior:
      An error message is shown saying that the size of the domain is more than permitted.

      Show
      1. in the master portal, go to Accounts > Create 2. Enter all fields correctly, and set the maximum size for the Org Name field (255 chars) 3. Click Create Account Actual behavior: The page gets reloaded and no error message is shown. Expected behavior: An error message is shown saying that the size of the domain is more than permitted.

    Description

      Similar to https://issues.redhat.com/browse/THREESCALE-7540 but when the org name is too long.

      There is a validation on the org_name filed, with maximum length of 255, and also the form for creating a tenant only allows a maximum of 255 characters.

      However, if the org name is close to the maximum limit, when the tenant account is created, the creation fails because the generated domain and admin domain validation fails, which only allows 255 characters also.

      The error internally is:

      {:account=>["Domain is too long (maximum is 255 characters)", "Admin domain is too long (maximum is 255 characters)"]}
      

      The issue here is that there is no field for domains in the tenant create form, so it's not clear where to show the message.
      Another thing is that the final size of the domain fields depend on the wildcard domain, so we can't calculate that beforehand.

      I think we need some analysis from the UX team on how to handle this.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rhn-support-dmayorov Daria Mayorova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: