How to add project based jenkings authorisation on your build server. This shows the benefits and the caveats of using this approach to secure your build server projects so that people can only view what they are authorised to view.

1. Jenkins
Authorisation
Improving Project Security / Isolation

2. - Different customers with different projects
running on one Jenkins instance
- Each customer can see all projects
- Security issues with viewing of code
- Confidence issues of project importance
Problem

3. - Each user has unique login credentials
- Segregate projects based on user
- Create admins (us) to view all projects
- Project based Matrix Authorisation
Strategy
Solution

4. Implementation - Enable It

5. - Can view all projects
- Can auth other users
- CRUD projects
- Manage Jenkins
Add Admin User
any Jenkins username

6. - Anyone auth'd to login
- Viewing of Jenkins Dashboard
- Viewing of other users
Add Authenticated Users
Add Group - anyone auth'd to access Jenkins

7. - Can view this project on dashboard
- Can View project specifics
Add Project Based Authentication

8. Admin user
Dashboard after Matrix Auth
Setup
Project specific user