jenkinsci / jenkinsci/script-security-plugin

[JENKINS-35065] Let whitelists be defined with wildcards

Open
#688 2 comments 0 reactions 0 assignees View on GitHub
component:script-security-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
76
Forks
181
Avg merge
14h 55m
Merged PRs (30d)
3

Description

Currently I need to specify each method that I want to get white-listed. This is extremely cumbersome. It would be helpful if I can use some kind of wildcards to specify the whitelist of a plug-in.

This basically is related to JENKINS-25804">JENKINS-25804. Why do I need to add every method on String to be whitelisted? It would be much simpler to say method * of String so that all methods on this immutable class get white listed (or even better: everything of String or Matcher, etc. is whitelisted). It shouldn't be hard to gather the matching methods using reflection.

---
Originally reported by drulli, imported from: Let whitelists be defined with wildcards


  • assignee: jglick
  • status: Open
  • priority: Major
  • component(s): script-security-plugin
  • resolution: Unresolved
  • votes: 3
  • watchers: 4
  • imported: 2025-12-09

Raw content of original issue

Currently I need to specify each method that I want to get white-listed. This is extremely cumbersome. It would be helpful if I can use some kind of wildcards to specify the whitelist of a plug-in.

This basically is related to JENKINS-25804. Why do I need to add every method on String to be whitelisted? It would be much simpler to say method * of String so that all methods on this immutable class get white listed (or even better: everything of String or Matcher, etc. is whitelisted). It shouldn't be hard to gather the matching methods using reflection.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.