Skip to content

[JENKINS-62448] Enhance information displayed in Script approval page #852

Description

@jenkins-infra-bot

Scope: Concerns only full script approval, not the signature or class path entry. (different scope from JENKINS-60682">JENKINS-60682)

In the current version of the "In-process Script Approval" page, you have the possibility to approve/deny a script and then, once approved, you can only revoke all approvals at once. This is not a very conveniant way to keep a healthy / reduced approved list.  It complicates administration and exposes the instance to potential security concerns due to obsolete scripts.

For that reason, we invested some time to provide new features to that page, especially around the full script approval part. Now, you have the possibility to approve / deny script in bulk. Also, to ease your approval, you have some new information displayed like the date of last use or the date of the approval request.
In addition to that, to better manage your approvals list, we are gathering some metadata on the script instead of just the hashes. They are displayed (when available) to help you understand where the different script are used, and more importantly when and how many times. This will help you make informed decision about the revocation of old / legacy approvals to keep the list humainly readable.


Originally reported by wfollonier, imported from: Enhance information displayed in Script approval page
  • assignee: wfollonier
  • status: Open
  • priority: Major
  • component(s): script-security-plugin
  • label(s): management, roadmap, ux
  • resolution: Unresolved
  • votes: 4
  • watchers: 6
  • imported: 2025-12-09
Raw content of original issue

Scope: Concerns only full script approval, not the signature or class path entry. (different scope from JENKINS-60682)

In the current version of the "In-process Script Approval" page, you have the possibility to approve/deny a script and then, once approved, you can only revoke all approvals at once. This is not a very conveniant way to keep a healthy / reduced approved list.  It complicates administration and exposes the instance to potential security concerns due to obsolete scripts.

For that reason, we invested some time to provide new features to that page, especially around the full script approval part. Now, you have the possibility to approve / deny script in bulk. Also, to ease your approval, you have some new information displayed like the date of last use or the date of the approval request. In addition to that, to better manage your approvals list, we are gathering some metadata on the script instead of just the hashes. They are displayed (when available) to help you understand where the different script are used, and more importantly when and how many times. This will help you make informed decision about the revocation of old / legacy approvals to keep the list humainly readable.

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for Enhancement.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions