Legacy token for user "unknown" keeps reappearing

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: core
    • Environment:
      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-setting.png
          legacy-setting.png
          22 kB
        2. legacy-warn.png
          legacy-warn.png
          20 kB
        3. plugins.txt
          5 kB
        4. plugins-merged.lieverdink.kolinek.froque.txt
          1 kB
        5. plugins-merged.txt
          1 kB
        6. unknown-user.png
          unknown-user.png
          71 kB

            Assignee:
            Wadeck Follonier
            Reporter:
            Peter Lieverdink
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: