[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev updated JENKINS-23500 ACL to protect some artifacts Change By: Oleg Nenashev (27/Sep/14 5:41 PM) Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Daniel Beck commented on JENKINS-23500 ACL to protect some artifacts Except that there's no real model object the permissions could be attached to. It'd also work very differently from existing authorization mechanisms (except maybe Role Strategy). There's very little value in exchange for a large effort here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev commented on JENKINS-23500 ACL to protect some artifacts @Brian Actually, the permission exists in experimental features (JENKINS-7765). Probably, it still works in newest versions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Daniel Beck commented on JENKINS-23500 ACL to protect some artifacts Oleg: Artifacts permission works, I'm using it and cannot imagine not doing so. However, it's all-or-nothing. You can have users with Item.Read and without Artifacts permission, and users with both Item.Read and Artifacts permission, but that's it. Far less granular than what this request is about. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev updated JENKINS-23500 ACL to protect some artifacts Currently, Jenkins do not provide permission control hooks on artifact level. BTW, such extension could be useful. Change By: Oleg Nenashev (29/Jun/14 8:09 PM) Summary: acl ACLto protectsomeartifacts Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev updated JENKINS-23500 ACL to protect some artifacts Change By: Oleg Nenashev (29/Jun/14 8:10 PM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Daniel Beck commented on JENKINS-23500 ACL to protect some artifacts IMO this is a horrible idea. Interaction with downstream jobs (e.g. Copy Artifact) would be quite complex (QueueItemAuthenticator?) and any change could have severe unexpected side effects. Just publish the public artifacts somewhere else and restrict access within Jenkins to trusted users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev commented on JENKINS-23500 ACL to protect some artifacts The case is similar to build-specific permissions... It just proposes an additional security atomization within an item. I don't think the idea is horrible. But it would require a very significant update in the quite legacy Artifacts mechanism. I think it could be done if somebody decouples it to a separate plugin (the mission seems to be impossible) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
