Connect to Jenkins using API token authentication

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • Connect to Jenkins using API token authentication instead of user name and password.

    Antes de Iniciar

    Role required:
    • Jenkins: admin or any user with overall Read and Job Read roles

    Por Que e Quando Desempenhar Esta Tarefa

    You can have multiple active API tokens at the same time and track the usage of your tokens. You can also revoke API tokens as needed. You can also use the Jenkins API token for authentication when you're using the Jenkins CLI.

    Procedimento

    1. In the Jenkins banner frame, select your user name to open the user menu.
    2. Select Security. Security page for a Jenkins user
    3. In the Security page, select Add new Token.
    4. Select Generate.
    5. Copy the API token that is generated
      Nota:
      • Regenerate the tokens every 6 months (depending on your context). Jenkins displays an indicator concerning the age of the token
      • Use a different token for each application so that if an application is compromised you can revoke its token individually.
      • If your token expires, regenerate the token and update it in the ServiceNow AI Platform instance
      • ServiceNow DevOps DevOps does not support using Legacy API Tokens because Jenkins does not recommend the use of Legacy API Token. For more information, see the Jenkins blog post.