After installing the suggested plugins in the setup wizard, the user is asked specify admin user credentials and name.

      None of these fields is marked as required, but leaving the E-Mail address field empty freezes the setup wizard after hitting Save and Finish.

      The request triggers the following exception output:

      Jul 09, 2017 1:56:38 PM hudson.init.impl.InstallUncaughtExceptionHandler$1 reportException
      WARNING: null
      java.io.IOException: finished
       at com.jcraft.jzlib.DeflaterOutputStream.write(DeflaterOutputStream.java:90)

      As the setup wizard disables all buttons, the only chance for the user is to reload the page (which allows the user to think again and enter more values and finally successfully finish the wizard).

      While the POST request to 

      /setupWizard/createAdminUser

      is actually responded with 200 OK, its HTML body containing the message Invalid e-mail address is not displayed to the user (only visible using the developer tools).

       

          [JENKINS-45387] Setup wizard hangs when email not entered

          Steffen Gebert created issue -
          Steffen Gebert made changes -
          Attachment New: JENKINS-45387-stacktrace.txt [ 38802 ]
          Daniel Beck made changes -
          Labels Original: exception setup New: exception newbie-friendly setup

          I'm able to reproduce this as well.

          MICHAEL PERZEL added a comment - I'm able to reproduce this as well.
          Janne Kanniainen made changes -
          Assignee New: Janne Kanniainen [ jkanniai ]
          Janne Kanniainen made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Janne Kanniainen made changes -
          Assignee Original: Janne Kanniainen [ jkanniai ]
          Janne Kanniainen made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]

          Philipp Nowak added a comment - - edited

          I think I have identified the issue and am working on a Pull Request with a fix.

          Basically, the SetupWizard calls the security realm for validation of the entered data, but that method already sends a response, so the SetupWizard can't send another response. (This causes the stack trace)

          Also, the frontend part is doing some black magic with iframes that seems to be blocked by at least Chrome (XSS; This causes the response to not show in the browser) and doesn't re-enable the buttons after an error response. (This causes the buttons being greyed out)

          Philipp Nowak added a comment - - edited I think I have identified the issue and am working on a Pull Request with a fix. Basically, the SetupWizard calls the security realm for validation of the entered data, but that method already sends a response, so the SetupWizard can't send another response. (This causes the stack trace) Also, the frontend part is doing some black magic with iframes that seems to be blocked by at least Chrome (XSS; This causes the response to not show in the browser) and doesn't re-enable the buttons after an error response. (This causes the buttons being greyed out)

          Philipp Nowak added a comment -

          Philipp Nowak added a comment - Here's the pull request:  https://github.com/jenkinsci/jenkins/pull/3116

            xxyy Philipp Nowak
            stephenking Steffen Gebert
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: