Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53266

Legacy token for user "unknown" keeps reappearing

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None
    • Jenkins versions 2.130 through 2.140 alpine docker image.

      Ever since the API token change introduced by JENKINS-32776, a legacy token is automagically generated on our install for the nonexistent user "unknown".

      Legacy tokens have been disabled since updating to 2.130.

      After manually revoking the token, it usually takes a few hours for it to magically reappear and then causes the red administrative monitor counter to (re-)appear in the toolbar.

      Though I can revoke the token, I am unable to change it via the user admin page Change API Token button.

        1. legacy-warn.png
          legacy-warn.png
          20 kB
        2. legacy-setting.png
          legacy-setting.png
          22 kB
        3. unknown-user.png
          unknown-user.png
          71 kB
        4. plugins.txt
          5 kB
        5. plugins-merged.txt
          1 kB
        6. plugins-merged.lieverdink.kolinek.froque.txt
          1 kB

          [JENKINS-53266] Legacy token for user "unknown" keeps reappearing

          Peter Lieverdink created issue -

          Oleg Nenashev added a comment -

          Oleg Nenashev added a comment - CC wfollonier
          Oleg Nenashev made changes -
          Assignee New: Wadeck Follonier [ wfollonier ]

          cafuego thank you for your report. Could you provide us the list of plugin and their version you currently have installed? This will help us investigating the case.

          Thank you in advance

          Wadeck Follonier added a comment - cafuego thank you for your report. Could you provide us the list of plugin and their version you currently have installed? This will help us investigating the case. Thank you in advance
          Peter Lieverdink made changes -
          Attachment New: plugins.txt [ 43918 ]

          Indeed I can, here is the full list: plugins.txt

          Peter Lieverdink added a comment - Indeed I can, here is the full list:  plugins.txt

          Thank you cafuego for the quick answer, I will try to reproduce the case as soon I have time and keep you informed.

          Wadeck Follonier added a comment - Thank you cafuego for the quick answer, I will try to reproduce the case as soon I have time and keep you informed.
          Peter Kolínek made changes -
          Attachment New: plugins-merged.txt [ 45077 ]

          I have the same issue. The "unknown" token reappears after every restart of Jenkins. I've created the list of plugins that are present on my instance AND in list provided by cafuego: plugins-merged.txt. Hopefully this will help to narrow the search.

           

          Peter Kolínek added a comment - I have the same issue. The "unknown" token reappears after every restart of Jenkins. I've created the list of plugins that are present on my instance AND in list provided by cafuego : plugins-merged.txt . Hopefully this will help to narrow the search.  

          Emil Styrke added a comment -

          wfollonier I have this issue too. I have all the plugins from the "merged" set except "Build Pipeline Plugin", "Build Timeout", "Email Extension Plugin", "Environment Injector Plugin" and "Windows Slaves Plugin".

          Emil Styrke added a comment - wfollonier I have this issue too. I have all the plugins from the "merged" set except "Build Pipeline Plugin", "Build Timeout", "Email Extension Plugin", "Environment Injector Plugin" and "Windows Slaves Plugin".

            wfollonier Wadeck Follonier
            cafuego Peter Lieverdink
            Votes:
            8 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: