| Chapter 23. Luntbuild Security | ||
|---|---|---|
 |  | |
| Chapter 23. Luntbuild Security | ||
|---|---|---|
| | | |
Table of Contents
Luntbuild has build-in security for user authentication and authorization handling. To be independent of the servlet container (application server) Luntbuild is installed in, all configuration is done inside the Luntbuild application itself.
Only authenticated users are allowed access to Luntbuild. Luntbuild functions are assigned following basic roles:
| site admin |
| project admin |
| project builder |
| project viewer |
| role description |
This role is intended to represent the root user. A user with an assigned role site-admin has unrestricted access to all of the Luntbuild's functionality. Following are the tasks the site admin is allowed to execute:
| user management |
| global property management |
| create projects |
| manage schedules |
| assign site-admin role to different users |
| assign project admin role to different users |
| inspect system log |
This role covers functionality for project management. Following are the tasks the project admin is allowed to execute:
| modify project settings |
| manage VCS modules |
| manage builds |
| assign users to project internal roles |
This role is restricted to managing the build related tasks. Following are the tasks the project builder is allowed to execute:
| manually trigger builds |
| assign build schedules |
| manage build results |
This is the most restrictive role. Following are the tasks the project viewer is allowed to execute:
| view build results |
| view build log |
| download build artifacts |
| | | |
| Chapter 22. Debugging Build Problems |  | How to configure security for Luntbuild. |