Security in Jenkins

Session Type: 
Standard [35 minutes]

Anyone setting up continuous integration using the popular Jenkins (or Hudson) server for more than a handful of people will soon need to consider security. How can you be identified to the server? How do your SCM commits get associated with that identity? Who should be allowed to do what? And how can Jenkins identify itself to other services, like GitHub or Maven repositories, when it needs to publish results?

Come see demos of different plugins that allow Jenkins to work with security and identity systems. Besides an overview of the most common authentication realms and authorization strategies, you may hear about user identity consolidation tools; role-based access control with the CloudBees enterprise edition of Jenkins; credential management for SSH and other outbound requests; Java keystore management; or accessing secure Jenkins content remotely using API tokens.

Schedule info



ALM Connect
Experience level: 

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.