Admin user access

Prev Next

AppGate ZTNA is managed using the admin UI or REST API calls. To access the admin UI, administrators and API users must be able to reach port 8443, have an account in an external identity provider (IdP) or the local IdP, and be assigned the appropriate privileges through an admin role.

Modern day enterprise-wide deployments must be supportable. Distributed local support with specific management rights helps teams operate across time zones. You can delegate access management to experts for different hosting domains and business networks (including AWS and Azure), and you can allow other systems and DevOps environments to provision access automatically as needed. For these reasons, the administration environment should be both role-based and API-based, with the same level of granularity as user access management.

Admin access is typically required to:

  • Perform admin tasks in the admin UI.

  • Make API calls to the Controller.

  • View audit logs in the LogServer.

  • Manage appliances using SSH.

We recommended creating additional admin accounts (including some in the local database) as soon as possible for redundancy and to maintain access.


Master system administrator account

AppGate ZTNA includes one preconfigured system administrator account (username “admin”) with full system administration privileges. Do not delete this account.

After the Controller is initialized and configured, you can sign in to the admin UI as "admin". The password for "admin" is created when configuring the first appliance.


Using the admin UI

The admin UI is built in and is available by signing in to the Controller UI at https://myserver.mycompany.com:8443/ui.

Multiple administrators can work in the admin UI at the same time. Database changes are managed at the object level, so administrators can edit different objects concurrently. If you use HA Controllers, we recommend that all administrators work on the same Controller.

All users who sign in to the Controller UI see the admin UI dashboard and menu options. However, what appears in the main window depends on the user’s admin roles and privileges. For example, an administrator with restricted privileges might see only certain policies, entitlements, and appliance information—or nothing—if no admin role is assigned.

AppGate ZTNA uses admin profiles to save each administrator’s preferences, such as the selected light or dark theme.


Using API-based administration

Admin roles also apply to REST API calls. For details, see REST API.


Record of administration actions

All actions performed by an administrator are recorded in logs and are associated with the user performing the action. For example:

t event_type on_boarded_device_deleted

For a full list of log record types, see Audit logs.


Propagating changes to administrators

Admin roles define the privileges (for example, editing policies, deleting policies, or revoking tokens) that can be performed from the Admin UI. Admin roles are assigned to administrators using policies, similar to user entitlements. After an administrator signs in to the Admin UI, their admin roles are listed in their entitlement token. The roles remain valid until the administrator signs out (ending the session), the entitlement token expires, or the entitlement is renewed—whichever occurs first.

Renewing an administrator’s entitlement token ends the session, and the administrator must sign in again. Any unsaved changes to system settings are lost. We recommend providing a warning before renewing a token so administrators have time to save their changes.