Bamboo throws 'Access denied' when attempting to deploy
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When attempting to deploy a release, 'Access denied Sorry, you have insufficient permissions to view the page' is seen in the browser. The user or group has proper permissions for the deployment project and environment.
The following appears in the atlassian-bamboo.log:
1
2
2016-08-18 12:32:45,399 INFO [http-nio-8085-exec-70] [AccessLogFilter] username GET http://bamboo/deploy/selectVersionForExecute.action?environmentId=11111111&returnUrl=/deploy/viewDeploymentProjectEnvironments.action?id=11111111 1052337kb
2016-08-18 12:32:45,416 WARN [http-nio-8085-exec-70] [AuthorizationLoggerListener] Authorization failed: org.acegisecurity.AccessDeniedException: Access is denied; authenticated principal: org.acegisecurity.adapters.PrincipalAcegiUserToken@e5aa7892: Username: username; Password: [PROTECTED]; Authenticated: true; Details: null; Granted Authorities: ROLE_USER; secure object: ReflectiveMethodInvocation: public abstract java.util.List com.atlassian.bamboo.plan.cache.CachedPlanManager.getBranchesForChain(com.atlassian.bamboo.plan.PlanIdentifier); target is of class [com.atlassian.bamboo.plan.cache.CachedPlanManagerImpl]; configuration attributes: [ACL_BUILD_READ]Cause
The user or group does not have proper permissions to the build plan.
Resolution
Despite having appropriate environment and deployment project permission, it is necessary for the user/group to have read permisssion to the respective build plan. Thus, grant 'View' permission to the affected user or group in the respective build plan and you should not see the error while deploying.
Was this helpful?