Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-7371

Customers receives repeated CAPTCHA loop prompts on sign up page for a Jira Service Desk Portal account

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Low Low
    • None
    • 4.13.4
    • Customer Portal
    • None

      Issue Summary

      Customers receives repeated CAPTCHA loop prompts on sign up page for a Jira Service Desk Portal account

      Steps to Reproduce

      1. Click on 'Sign up for an account' in customer portal login page
      2. Should result in http://localhost:port/jxxx/servicedesk/customer/user/signup
      3. Entering a valid email address and the correct CAPTCHA will repeat indefinitely in a loop without allowing the Sign up

       Issue is not replicable at every attempt, could replicate locally once after multiple attempts

      Expected Results

      Customers should be able to Sign up on the first attempt

      Actual Results

      Customers receives repeated CAPTCHA loop prompts on Sign up

      Workaround

      Workaround1: Delete the browser cookies

      User receives repeated CAPTCHA prompts on login to Jira server

      Workaround2:

      Navigate to ⚙️ → Applications → Configurations → Under 'Public signup' → Choose 'No, customers can just sign up'

        1. image-2021-05-12-20-21-55-326.png
          image-2021-05-12-20-21-55-326.png
          50 kB
        2. image-2021-05-12-20-23-52-429.png
          image-2021-05-12-20-23-52-429.png
          125 kB
        3. image-2021-05-12-20-30-04-292.png
          image-2021-05-12-20-30-04-292.png
          308 kB
        4. Screen Shot 2021-05-13 at 12.13.46 pm.png
          Screen Shot 2021-05-13 at 12.13.46 pm.png
          140 kB
        5. SDS-58748.har
          241 kB

            [JSDSERVER-7371] Customers receives repeated CAPTCHA loop prompts on sign up page for a Jira Service Desk Portal account

            Hi Support,

            We were looking to use the customer email verification.

            We've installed version 4.13.7 in our development environment and we're experiencing this issue. Workaround 1 doesn't work and Workaround 2 just puts us back to where we were. 

            Basically, the "Yes, customers should verify their emails" feature for Public Signup is nonexistent.

            We would also like to see this fixed.

            Thanks.

            MadelineBarr added a comment - Hi Support, We were looking to use the customer email verification. We've installed version 4.13.7 in our development environment and we're experiencing this issue. Workaround 1 doesn't work and Workaround 2 just puts us back to where we were.  Basically, the "Yes, customers should verify their emails" feature for Public Signup is nonexistent. We would also like to see this fixed. Thanks.

            Hi Support,

            This is affecting our clients. Currently workaround resolved the issue, but with it we can't have verification of the email on.

            It looks like that project customer permissions in combination with public signup (and setup related to email verification) are in conflict, resulting in a bug. We have more than 50 JSM projects where options for customer permissions vary per project (all three oprtins are used in our instance).

            Please fix this.

            Thanks in advance!

            Bojana Vasic added a comment - Hi Support, This is affecting our clients. Currently workaround resolved the issue, but with it we can't have verification of the email on. It looks like that project customer permissions in combination with public signup (and setup related to email verification) are in conflict, resulting in a bug. We have more than 50 JSM projects where options for customer permissions vary per project (all three oprtins are used in our instance). Please fix this. Thanks in advance!

              Unassigned Unassigned
              skattamuru@atlassian.com Sriteja Kattamuru (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: