• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • Jenkins 2.405 or later with plugins:
      bouncycastle-api:2.28
      credentials:1254.vb_96f366e7b_a_d
      instance-identity:173.va_37c494ec4e5
      javax-activation-api:1.2.0-6
      javax-mail-api:1.6.2-9
      structs:324.va_f5d6774f3a_d
    • 2.410

      When i try to delete users from the trash can icon on the "Manage Jenkins" / "Users" page with the "Jenkins own user database" security realm, I get a 404 error and the user is not deleted.

      HTTP ERROR 404 Not Found
      URI:/manage/securityRealm/user/gkalisse/delete STATUS:404 MESSAGE:Not Found SERVLET:Stapler

        1. image-2023-06-13-05-50-44-823.png
          image-2023-06-13-05-50-44-823.png
          123 kB
        2. image-2023-06-12-15-56-03-480.png
          image-2023-06-12-15-56-03-480.png
          71 kB
        3. image-2023-06-12-15-55-01-953.png
          image-2023-06-12-15-55-01-953.png
          50 kB
        4. screenshot-1.png
          screenshot-1.png
          78 kB
        5. plugins-1.txt
          0.2 kB
        6. run-jenkins.sh
          0.8 kB
        7. plugins.txt
          3 kB

          [JENKINS-71429] Deleting a user fails with HTTP 404

          Mark Waite added a comment -

          ccheltenham you'll need to provide more information so that others can duplicate the issue. I'm running Jenkins 2.401.1 on a Debian based container using the "Jenkins own user database" security realm and have no issue deleting users from the "Manage Jenkins" -> "User" page (URL /manage/securityRealm/).

          Please provide the information listed in "How to report an issue" so that others are more likely to investigate the issue you are reporting.

          Mark Waite added a comment - ccheltenham you'll need to provide more information so that others can duplicate the issue. I'm running Jenkins 2.401.1 on a Debian based container using the "Jenkins own user database" security realm and have no issue deleting users from the "Manage Jenkins" -> "User" page (URL /manage/securityRealm/). Please provide the information listed in "How to report an issue" so that others are more likely to investigate the issue you are reporting.

          If I got to dashboard -->manage -->users -->
          click on the trashcan to the right of an employee that left.

          I get this error -
          HTTP ERROR 404 Not Found
          URI: /manage/securityRealm/user/gkalisse/delete
          STATUS: 404
          MESSAGE: Not Found
          SERVLET: Stapler

          Chris Cheltenham added a comment - If I got to dashboard -->manage -->users --> click on the trashcan to the right of an employee that left. I get this error - HTTP ERROR 404 Not Found URI: /manage/securityRealm/user/gkalisse/delete STATUS: 404 MESSAGE: Not Found SERVLET: Stapler

          Mark Waite added a comment -

          Please provide the information listed in "How to report an issue" so that others are more likely to investigate the issue you are reporting.

          Mark Waite added a comment - Please provide the information listed in "How to report an issue" so that others are more likely to investigate the issue you are reporting.

          Jenkins: 2.409
          OS: Linux - 6.1.0-9-cloud-amd64
          Java: 17.0.6 - Debian (OpenJDK 64-Bit Server VM)
          —
          ace-editor:1.1
          antisamy-markup-formatter:159.v25b_c67cd35fb_
          apache-httpcomponents-client-4-api:4.5.14-150.v7a_b_9d17134a_5
          authentication-tokens:1.53.v1c90fd9191a_b_
          azure-ad:349.vc02b_a_0b_142a_8
          azure-sdk:132.v62b_48eb_6f32f
          bitbucket:223.vd12f2bca5430
          bootstrap5-api:5.3.0-1
          bouncycastle-api:2.26
          branch-api:2.1071.v1a_188a_562481
          build-name-setter:2.2.0
          build-timeout:1.24
          caffeine-api:3.1.6-115.vb_8b_b_328e59d8
          checks-api:2.0.0
          cloudbees-bitbucket-branch-source:791.vb_eea_a_476405b
          cloudbees-folder:6.815.v0dd5a_cb_40e0e
          command-launcher:100.v2f6722292ee8
          commons-lang3-api:3.12.0-36.vd97de6465d5b_
          commons-text-api:1.10.0-36.vc008c8fcda_7b_
          config-file-provider:3.11.1
          credentials:1254.vb_96f366e7b_a_d
          credentials-binding:604.vb_64480b_c56ca_
          data-tables-api:1.12.1-4
          display-url-api:2.3.7
          docker-commons:419.v8e3cd84ef49c
          docker-java-api:3.2.13-37.vf3411c9828b9
          docker-plugin:1.2.9
          durable-task:500.v8927d9fd99d8
          echarts-api:5.4.0-5
          embeddable-build-status:255.va_d2370ee8fde
          font-awesome-api:6.4.0-1
          gcloud-sdk:0.0.3
          git:4.11.5
          git-client:3.11.2
          google-oauth-plugin:1.0.8
          gradle:1.39.4
          h2-api:11.1.4.199-12.v9f4244395f7a_
          handlebars:3.0.8
          handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953
          instance-identity:142.v04572ca_5b_265
          ionicons-api:56.v1b_1c8c49374e
          jackson2-api:2.15.2-350.v0c2f3f8fc595
          jakarta-activation-api:2.0.1-3
          jakarta-mail-api:2.0.1-3
          javax-activation-api:1.2.0-6
          javax-mail-api:1.6.2-9
          jaxb:2.3.8-1
          jdk-tool:66.vd8fa_64ee91b_d
          jquery3-api:3.7.0-1
          jsch:0.2.8-65.v052c39de79b_2
          junit:1207.va_09d5100410f
          lockable-resources:1117.v157231b_03882
          mailer:457.v3f72cb_e015e5
          matrix-auth:3.1.5
          matrix-project:789.v57a_725b_63c79
          mercurial:1260.vdfb_723cdcc81
          mina-sshd-api-common:2.9.1-44.v476733c11f82
          mina-sshd-api-core:2.9.1-44.v476733c11f82
          momentjs:1.1.1
          nodejs:1.6.0
          oauth-credentials:0.645.ve666a_c332668
          okhttp-api:4.9.3-108.v0feda04578cf
          pipeline-build-step:491.v1fec530da_858
          pipeline-graph-analysis:202.va_d268e64deb_3
          pipeline-groovy-lib:656.va_a_ceeb_6ffb_f7
          pipeline-input-step:468.va_5db_051498a_4
          pipeline-maven:1298.v43b_82f220a_e9
          pipeline-milestone-step:111.v449306f708b_7
          pipeline-model-api:2.2133.ve46a_6113dfc3
          pipeline-model-definition:2.2114.v2654ca_721309
          pipeline-model-extensions:2.2133.ve46a_6113dfc3
          pipeline-rest-api:2.32
          pipeline-stage-step:305.ve96d0205c1c6
          pipeline-stage-tags-metadata:2.2114.v2654ca_721309
          pipeline-stage-view:2.32
          pipeline-utility-steps:2.15.4
          plain-credentials:143.v1b_df8b_d3b_e48
          plugin-util-api:3.3.0
          popper2-api:2.11.6-2
          rebuild:320.v5a_0933a_e7d61
          resource-disposer:0.22
          scm-api:672.v64378a_b_20c60
          script-security:1251.vfe552ed55f8d
          slack:664.vc9a_90f8b_c24a_
          snakeyaml-api:1.33-95.va_b_a_e3e47b_fa_4
          ssh-credentials:305.v8f4381501156
          ssh-slaves:2.877.v365f5eb_a_b_eec
          sshd:3.249.v2dc2ea_416e33
          structs:324.va_f5d6774f3a_d
          throttle-concurrents:2.13
          timestamper:1.25
          token-macro:359.vb_cde11682e0c
          trilead-api:2.84.v72119de229b_7
          variant:59.vf075fe829ccb
          workflow-aggregator:596.v8c21c963d92d
          workflow-api:1213.v646def1087f9
          workflow-basic-steps:1017.vb_45b_302f0cea_
          workflow-cps:3673.v5b_dd74276262
          workflow-durable-task-step:1247.v7f9dfea_b_4fd0
          workflow-job:1308.v58d48a_763b_31
          workflow-multibranch:746.v05814d19c001
          workflow-scm-step:408.v7d5b_135a_b_d49
          workflow-step-api:639.v6eca_cd8c04a_a_
          workflow-support:839.v35e2736cfd5c
          ws-cleanup:0.45

          Chris Cheltenham added a comment - Jenkins: 2.409 OS: Linux - 6.1.0-9-cloud-amd64 Java: 17.0.6 - Debian (OpenJDK 64-Bit Server VM) — ace-editor:1.1 antisamy-markup-formatter:159.v25b_c67cd35fb_ apache-httpcomponents-client-4-api:4.5.14-150.v7a_b_9d17134a_5 authentication-tokens:1.53.v1c90fd9191a_b_ azure-ad:349.vc02b_a_0b_142a_8 azure-sdk:132.v62b_48eb_6f32f bitbucket:223.vd12f2bca5430 bootstrap5-api:5.3.0-1 bouncycastle-api:2.26 branch-api:2.1071.v1a_188a_562481 build-name-setter:2.2.0 build-timeout:1.24 caffeine-api:3.1.6-115.vb_8b_b_328e59d8 checks-api:2.0.0 cloudbees-bitbucket-branch-source:791.vb_eea_a_476405b cloudbees-folder:6.815.v0dd5a_cb_40e0e command-launcher:100.v2f6722292ee8 commons-lang3-api:3.12.0-36.vd97de6465d5b_ commons-text-api:1.10.0-36.vc008c8fcda_7b_ config-file-provider:3.11.1 credentials:1254.vb_96f366e7b_a_d credentials-binding:604.vb_64480b_c56ca_ data-tables-api:1.12.1-4 display-url-api:2.3.7 docker-commons:419.v8e3cd84ef49c docker-java-api:3.2.13-37.vf3411c9828b9 docker-plugin:1.2.9 durable-task:500.v8927d9fd99d8 echarts-api:5.4.0-5 embeddable-build-status:255.va_d2370ee8fde font-awesome-api:6.4.0-1 gcloud-sdk:0.0.3 git:4.11.5 git-client:3.11.2 google-oauth-plugin:1.0.8 gradle:1.39.4 h2-api:11.1.4.199-12.v9f4244395f7a_ handlebars:3.0.8 handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953 instance-identity:142.v04572ca_5b_265 ionicons-api:56.v1b_1c8c49374e jackson2-api:2.15.2-350.v0c2f3f8fc595 jakarta-activation-api:2.0.1-3 jakarta-mail-api:2.0.1-3 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.8-1 jdk-tool:66.vd8fa_64ee91b_d jquery3-api:3.7.0-1 jsch:0.2.8-65.v052c39de79b_2 junit:1207.va_09d5100410f lockable-resources:1117.v157231b_03882 mailer:457.v3f72cb_e015e5 matrix-auth:3.1.5 matrix-project:789.v57a_725b_63c79 mercurial:1260.vdfb_723cdcc81 mina-sshd-api-common:2.9.1-44.v476733c11f82 mina-sshd-api-core:2.9.1-44.v476733c11f82 momentjs:1.1.1 nodejs:1.6.0 oauth-credentials:0.645.ve666a_c332668 okhttp-api:4.9.3-108.v0feda04578cf pipeline-build-step:491.v1fec530da_858 pipeline-graph-analysis:202.va_d268e64deb_3 pipeline-groovy-lib:656.va_a_ceeb_6ffb_f7 pipeline-input-step:468.va_5db_051498a_4 pipeline-maven:1298.v43b_82f220a_e9 pipeline-milestone-step:111.v449306f708b_7 pipeline-model-api:2.2133.ve46a_6113dfc3 pipeline-model-definition:2.2114.v2654ca_721309 pipeline-model-extensions:2.2133.ve46a_6113dfc3 pipeline-rest-api:2.32 pipeline-stage-step:305.ve96d0205c1c6 pipeline-stage-tags-metadata:2.2114.v2654ca_721309 pipeline-stage-view:2.32 pipeline-utility-steps:2.15.4 plain-credentials:143.v1b_df8b_d3b_e48 plugin-util-api:3.3.0 popper2-api:2.11.6-2 rebuild:320.v5a_0933a_e7d61 resource-disposer:0.22 scm-api:672.v64378a_b_20c60 script-security:1251.vfe552ed55f8d slack:664.vc9a_90f8b_c24a_ snakeyaml-api:1.33-95.va_b_a_e3e47b_fa_4 ssh-credentials:305.v8f4381501156 ssh-slaves:2.877.v365f5eb_a_b_eec sshd:3.249.v2dc2ea_416e33 structs:324.va_f5d6774f3a_d throttle-concurrents:2.13 timestamper:1.25 token-macro:359.vb_cde11682e0c trilead-api:2.84.v72119de229b_7 variant:59.vf075fe829ccb workflow-aggregator:596.v8c21c963d92d workflow-api:1213.v646def1087f9 workflow-basic-steps:1017.vb_45b_302f0cea_ workflow-cps:3673.v5b_dd74276262 workflow-durable-task-step:1247.v7f9dfea_b_4fd0 workflow-job:1308.v58d48a_763b_31 workflow-multibranch:746.v05814d19c001 workflow-scm-step:408.v7d5b_135a_b_d49 workflow-step-api:639.v6eca_cd8c04a_a_ workflow-support:839.v35e2736cfd5c ws-cleanup:0.45

          Debian 11
          It runs in docker container I believe.
          Its configured to use java 1.8 although there are java 11 and 17 installed here.
          I don't know why the devs use 1.8
          There is NO reverse proxy the certs are local.
          Installed jenkins with #apt install jenkins.
          We used chrome as a browser and FF i tried as well same results.

          Chris Cheltenham added a comment - Debian 11 It runs in docker container I believe. Its configured to use java 1.8 although there are java 11 and 17 installed here. I don't know why the devs use 1.8 There is NO reverse proxy the certs are local. Installed jenkins with #apt install jenkins. We used chrome as a browser and FF i tried as well same results.

          Mark Waite added a comment - - edited

          Thanks for the additional details. I can duplicate the issue with Jenkins 2.409, 2.407, 2.406, and 2.405, and cannot duplicate the issue with Jenkins 2.404 or 2.401.1.

          Steps that I took to duplicate the issue included:

          1. Create a file plugins.txt that lists the plugins and their versions
          2. Create a script run-jenkins.sh that runs Jenkins 2.409 with the plugin versions in plugins.txt
          3. Run the script on my Debian Linux (testing distro - very near Debian 12 at the moment)
          4. Open the web page (for example, http://localhost:8080) and enter the initial password that is displayed in the console window
          5. Choose to install no additional plugins from the setup wizard (selecting "None" from the "Choose plugins to install")
          6. Define a user for the administrator (in my case, I chose "mwaite" with a password and email address)
          7. Open "Manage Jenkins" / "Users" and add a user named "gkalisse"
          8. Delete the user "gkalisse" by clicking the trash can icon for that user on the "Manage Jenkins" / "Users" page

          When I follow those steps with Jenkins 2.401.1 or 2.404, the deletion happens as expected. When I follow those steps with Jenkins 2.405, 2.406, 2.407 or 2.409, the deletion fails with a page not found error (404).

          It appears the problem was inserted by commit 9d6f0743ba in Jenkins 2.405 that is part of PR 7911 - use dialogs to delete computers, views, clouds, users and logrecorders. There is draft pull request (work in progress) that is using the work from PR-7911 to take the next step to use a modal dialog inside the web page for deletions.

          Let's check with mawinter69 to see which direction he recommends should be taken, whether he can fix the user deletion code that is currently not working on 2.409 or if we should consider a revert of PR-7911 so that users can be deleted.

          Thanks again ccheltenham for providing the extra details so that the bug could be duplicated.

          Mark Waite added a comment - - edited Thanks for the additional details. I can duplicate the issue with Jenkins 2.409, 2.407, 2.406, and 2.405, and cannot duplicate the issue with Jenkins 2.404 or 2.401.1. Steps that I took to duplicate the issue included: Create a file plugins.txt that lists the plugins and their versions Create a script run-jenkins.sh that runs Jenkins 2.409 with the plugin versions in plugins.txt Run the script on my Debian Linux (testing distro - very near Debian 12 at the moment) Open the web page (for example, http://localhost:8080 ) and enter the initial password that is displayed in the console window Choose to install no additional plugins from the setup wizard (selecting "None" from the "Choose plugins to install") Define a user for the administrator (in my case, I chose "mwaite" with a password and email address) Open "Manage Jenkins" / "Users" and add a user named "gkalisse" Delete the user "gkalisse" by clicking the trash can icon for that user on the "Manage Jenkins" / "Users" page When I follow those steps with Jenkins 2.401.1 or 2.404, the deletion happens as expected. When I follow those steps with Jenkins 2.405, 2.406, 2.407 or 2.409, the deletion fails with a page not found error (404). It appears the problem was inserted by commit 9d6f0743ba in Jenkins 2.405 that is part of PR 7911 - use dialogs to delete computers, views, clouds, users and logrecorders . There is draft pull request (work in progress) that is using the work from PR-7911 to take the next step to use a modal dialog inside the web page for deletions. Let's check with mawinter69 to see which direction he recommends should be taken, whether he can fix the user deletion code that is currently not working on 2.409 or if we should consider a revert of PR-7911 so that users can be deleted. Thanks again ccheltenham for providing the extra details so that the bug could be duplicated.

          Mark Waite added a comment -

          The file plugins-1.txt shows the same issue with a much smaller set of plugins installed. Instructions in the earlier comment can be followed with the replacement of plugins.txt by plugins-1.txt

          Mark Waite added a comment - The file plugins-1.txt shows the same issue with a much smaller set of plugins installed. Instructions in the earlier comment can be followed with the replacement of plugins.txt by plugins-1.txt

          Markus Winter added a comment -

          Temporary workarounds:

          • click on the user to go to user page and click delete from there
          • click on user context menu chevron and select delete

           

          Markus Winter added a comment - Temporary workarounds: click on the user to go to user page and click delete from there click on user context menu chevron and select delete  

          I don;t understand this

          "click on the user to go to user page and click delete from there"

          If I click on the user, there's nothing there.

          Chris Cheltenham added a comment - I don;t understand this "click on the user to go to user page and click delete from there" If I click on the user, there's nothing there.

          manage --> users --> click on the trashcan?

          Chris Cheltenham added a comment - manage --> users --> click on the trashcan?

          If I click on the gear to the left of the trashcan i get this stuff.

           

          Chris Cheltenham added a comment - If I click on the gear to the left of the trashcan i get this stuff.  

          There's nothing in the page above I see that says to delete them.

          Chris Cheltenham added a comment - There's nothing in the page above I see that says to delete them.

          Markus Winter added a comment -

          There is a delete link in the side panel on the left. If you click there you can delete this user.

          Markus Winter added a comment - There is a delete link in the side panel on the left. If you click there you can delete this user.

          Markus, there is nothing in the left panel to delete users.

          Chris Cheltenham added a comment - Markus, there is nothing in the left panel to delete users.

          If I understand this resources, the fix for this is in the next release of 2.410.

           

          correct?

          Chris Cheltenham added a comment - If I understand this resources, the fix for this is in the next release of 2.410.   correct?

          Markus Winter added a comment -

          If you go to a specific user (click on the user directly or the gear) you have the delete link on the left. You have even posted the image above where the link is visible.

           

          Markus Winter added a comment - If you go to a specific user (click on the user directly or the gear) you have the delete link on the left. You have even posted the image above where the link is visible.  

          got it, thanks.

           

          Completely missed that, can't see the forest through the trees.

          Chris Cheltenham added a comment - got it, thanks.   Completely missed that, can't see the forest through the trees.

          I would say this case is closed. I thank you for your help Markus.

           

          Chris Cheltenham added a comment - I would say this case is closed. I thank you for your help Markus.  

            mawinter69 Markus Winter
            ccheltenham Chris Cheltenham
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: