Is your feature request related to a problem? Please describe.
Description
The Artifactory jenkins and JFrog jenkins plugins currently support system-wide credential configurations but lack the capability to specify credentials at the folder level. This limitation can cause security risks and unwanted cross-team deployments. The solution sought after involves restricting credentials to specific Jenkins folders to ensure that only authorized teams can deploy artifacts relevant to their projects.
Describe the solution you'd like to see
Feature description
Add support for configuring credentials at the Jenkins folder level within the Artifactory plugin. This includes:
Maintaining the system-wide instance URL configuration.
Allowing credentials to be defined within individual Jenkins folders.
Ensuring that these credentials are utilized only within the scope of the respective folders.
What is the expected behaviour
With folder-level credentials, the expected behavior is:
- The system-wide Artifactory instance URL remains unchanged and consistent across Jenkins.
- Credentials can be assigned and managed at the folder level.
- Deployments are restricted to authorized teams based on folder-level credentials, preventing cross-team access.
- Enhanced security and control over deployments, limiting them to specific projects or teams.
Describe alternatives you've considered
Possible workaround
Set up permission targets in Artifactory that define which repositories specific users/groups can access.
Use include/exclude patterns to fine-tune access controls and restrict artifact deployments to specific repositories or paths.
Additional context
No response
Is your feature request related to a problem? Please describe.
Description
The Artifactory jenkins and JFrog jenkins plugins currently support system-wide credential configurations but lack the capability to specify credentials at the folder level. This limitation can cause security risks and unwanted cross-team deployments. The solution sought after involves restricting credentials to specific Jenkins folders to ensure that only authorized teams can deploy artifacts relevant to their projects.
Describe the solution you'd like to see
Feature description
Add support for configuring credentials at the Jenkins folder level within the Artifactory plugin. This includes:
Maintaining the system-wide instance URL configuration.
Allowing credentials to be defined within individual Jenkins folders.
Ensuring that these credentials are utilized only within the scope of the respective folders.
What is the expected behaviour
With folder-level credentials, the expected behavior is:
Describe alternatives you've considered
Possible workaround
Set up permission targets in Artifactory that define which repositories specific users/groups can access.
Use include/exclude patterns to fine-tune access controls and restrict artifact deployments to specific repositories or paths.
Additional context
No response