Is your feature request related to a problem? Please describe.
When Xray blocks a package download in Jenkins due to a policy violation, the current error message displayed in Jenkins logs is a generic "403 Forbidden" error. This leads to confusion for users, as 403 errors typically indicate authorization issues. Users are forced to consult JFrog logs to determine the actual cause of the block (Xray policy violation), which adds unnecessary steps to troubleshooting and delays resolution.
Describe the solution you'd like to see
We request an enhancement to the error message displayed in Jenkins logs when Xray blocks a package download. Instead of a generic 403, the message should clearly indicate that the block is due to an Xray policy violation and provide relevant details.
Describe alternatives you've considered
Currently, the only workaround is for users to manually check the JFrog Artifactory and Xray logs whenever a 403 error is observed in Jenkins during package download.
Additional context
No response
Is your feature request related to a problem? Please describe.
When Xray blocks a package download in Jenkins due to a policy violation, the current error message displayed in Jenkins logs is a generic "403 Forbidden" error. This leads to confusion for users, as 403 errors typically indicate authorization issues. Users are forced to consult JFrog logs to determine the actual cause of the block (Xray policy violation), which adds unnecessary steps to troubleshooting and delays resolution.
Describe the solution you'd like to see
We request an enhancement to the error message displayed in Jenkins logs when Xray blocks a package download. Instead of a generic 403, the message should clearly indicate that the block is due to an Xray policy violation and provide relevant details.
Describe alternatives you've considered
Currently, the only workaround is for users to manually check the JFrog Artifactory and Xray logs whenever a 403 error is observed in Jenkins during package download.
Additional context
No response