Configuration with Application Deployment - Child permissions under AMPCORE not fully visible in dropdown

Technical Support
,
1

System Information

Field Value
Operating System Windows - Windows 10 Home on x86_64
Product AMPService ‘Phobos’ v2.6.0.10 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

I’m trying to create a role that allows some users to manage turning the servers on and off, as well as update them while I’m not available. However, I don’t want to grant them full access. The issue is that the parent permissions of AMPCORE do not fully support splitting these permissions into the child’s permissions below.

Reproduction Steps

  • Create a temporary role with the basic settings to log in.
  • Create a temporary user and assign them that role.
  • Enable all instances, then try to turn the server on and off.
  • Go under AMPCORE into the child’s permissions and enable all of them without enabling the parent permission AMPCORE above with Core*. Then try to turn the server on and off.
  • Now, fully enable the parent permission, AMPCORE, where it warns you with “Sensitive Permission Warning.” Once it’s enabled, try to turn the server on and off.
  • As you can see, you can only turn the server on and off with the parent permission, AMPCORE.
2

I’m one of the people helping with this problem and with the information we found. To provide further clarity regarding the issue:

Configuration Issue in Role Management:

We’ve discovered a configuration problem in the Role Management section, particularly under Local Instances. In this section, you can see the entities you are hosting and access options to enable, disable, start, stop, and restart them. However, these options will not function unless the parent permission, AMPCORE, is fully enabled. You can observe this behavior within Instances by attempting to locate and use the start, stop, and restart buttons.

They have provided detailed steps above to reproduce the issue and aid in troubleshooting. We hope this helps clarify the problem.

3

Two different things. From ADS under Local Instances the start, stop … are related to the instance. You need to manage the instance first and configure there start, stop … under AMPCore for the actual application managed by the instance.

4

Thank you for your input and guidance. I followed the provided steps, but unfortunately, the issue persists. The start, stop, and other instance management options are still not functioning as expected when attempting to configure them under AMPCORE without enabling the parent permission. This leads me to believe that the issue might be related to the Windows 10/11 version of the application.

Permissions for Test-Role under Global Settings:

I have fully enabled Login.

I have fully enabled ADS Config

I have fully enabled AMP Instance Manager

under AMPCore

I have fully enabled App Management actions to allow users to control the running application.

I have fully enabled all instances, including:

ADS (ADS01)

Test (MC)

& Other instances

I also tried enabling everything but the parent permission of AMPCore meaning everything inside of it is enabled but not the main switch of it but unfortunately, the issue persists.Visually, what I’m seeing on every browser with the test account logged in is as

follows:

Instances

Deployment Log

Configuration

On the blue bar labeled Local Instances, I only see the refresh button.

In a running test instance, under the instance box, I can see Manage:

When I click on Manage and go to the Status page, I only see:

Metrics and Status (CPU-Usage/Memory-Usage/Active-Users)

Actions Connection Info (IP and Network Port Status)

However, the buttons to start, stop, update, etc., are not showing up at all.

I wanted to provide you with the latest update v2.6.0.12, built 2/12/2025 The issue is still occurring, but we’ve found a workaround for now. Inside the Instances section, the big blue bar allows us to stop all, start all, and update all. However, these options are still not available within the manage button.

5

Manage the instance and go to configuration and then show the permissions you set inside the instance.

6

Maybe you also want to read through Managing user permissions in AMP

1 Like
7

Thank you for the information. I realize now that there are two Configuration areas. I was primarily focusing on the front Configuration and not the Instances Configuration, which can be accessed by clicking on Manage and then Configuration.