Unable to Assign Team Permissions for Execution Environments — Option Not Listed

Get Help
, , ,
1

Unable to Assign Team Permissions for Execution Environments — Option Not Listed.
Dear community,

We are currently using LDAP for managing user access and permissions in AWX. However, we’ve encountered what appear to be two limitations (or possibly bugs):

  1. Copy Button Not Visible for Non-Admin Users
    Users with the role “Normal User” are unable to see the copy icon for job templates, as shown below:

image
image2786×564 35 KB

  1. Non-Admin Users Cannot Access Execution Environments
    As an admin, I am able to view and select Execution Environments while running job templates.
    However, users with non-admin roles (like “Normal User”) do not see the all the custom Execution Environments during Job Template execution as shown below.

image
image2140×1219 136 KB

And infact they should all the custom EE created.

To address this, I attempted to grant access to Execution Environments by assigning permissions to an LDAP group (via Teams in AWX). Unfortunately, the “Add team permissions” dialog does not list Execution Environments as a resource type:

image
image2250×1524 140 KB

I found this related GitHub issue, which confirms that RBAC support for Execution Environments is currently lacking. I’ve tried looking for workarounds but haven’t been successful.

Note: If I create a user locally (Not through LDAP) and associate this user to the team , I can see the Execution Environments without any issues as shown below . (devops_awx_vault_lookup)

image
image2610×820 200 KB

If anyone has found a solution or workaround for this, I’d greatly appreciate your input.

Thank you!

Thanks and Regards
Saravana Selvaraj