I asked this question on Stack Overflow some time ago, and didn't get any satisfactory answers (http://stackoverflow.com/questions/14266434/jenkins-security-ii-deny-anonymous-access-but-allow-access-via-cli?lq=1), so I'm hoping this list will help me out. Basically, due to Jenkins' overly permissive policy of providing information to anonymous viewers, we need to lock down Jenkins. Unfortunately, locking down Jenkins by using matrix-based security to allow authenticated users to do everything and anonymous users to do nothing breaks access to the command-line API, because apparently authentication via SSH key does not count as a real authentication for the matrix-based security. Is there a way to set up matrix-based security to fix this, or is the only solution to switch from using SSH-based authentication to a specific user and password combination?
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
