◄
►

User Management - Operator

The User Management feature allows you to manage users, their roles, service permissions (formerly known as Role Customization), and authentication.

As an Operator, you can access this feature from the Operator portal, by navigating to Administration > User Management . The following screen is displayed:
Figure 1. User Management- Operator
The User Management window displays four tabs: Users, Roles, Service Permissions, and Authentication.
For additional information on each of these tabs, see:

Users

As an Operator, you can view the list of existing users and their corresponding details. You can add, modify, or delete a user. However, you cannot modify or delete an Operator Superuser. An Operator Super User can create new Operator users with different role privileges and configure API tokens for each Operator user.

To access the Users tab:

  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management.
    The Users tab is displayed by default.
    Figure 2. Users Tab
  3. On the Users screen, you can perform the following activities:
    Table 1. Users Tab- Options and Descriptions
    Option Description
    New User Creates a new Operator user. For additional information, see Add New User.
    Modify Allows you to modify the properties of the selected Operator user. You can also select the link to the username to modify the properties. You can change the Activation State of the selected Operator user. Only an Operator Super User can manage API tokens. For additional information, see API Tokens.
    Password Reset Sends an email to the selected user with a link to reset the password. You can also choose to freeze the account until the password is reset.
    Delete Deletes the selected user. You cannot delete the default users.
    More Select this option, and then select Download to download the details of all the users into a file in CSV format.

     

  4. The following are the other options available in the Users tab:
    Table 2. Additional Options
    Option Description
    Search Enter a search term to search for the matching text across the table. Use the advanced search option to narrow down the search results.
    Columns Select and select the columns to be displayed or hidden on the page.
    Refresh Select to refresh the page to display the most current data.

Add New User

In the Operator portal, you can add new users and configure the user settings. Only Operator Superusers and Operator Standard Admins can add a new user. To add a new user, perform the following steps:
  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management.
    The Users tab is displayed by default.
  3. Select New User.
    The following screen appears:
    Figure 3. Add New User
  4. Enter the following details for the new user:
    Table 3. Add New User- Options and Descriptions
    Option Description
    General Information Enter the required personal details of the user.
    Role Select a role that you want to assign to the user. For information on roles, see Roles.
    Edge Access Ensure that you have Operator Super User role to modify the Access Level for the user. Choose one of the following options:
    • Basic: Allows you to perform certain basic debug operations such as ping, tcpdump, PCAP, remote diagnostics, and so on.
    • Privileged: Grants you the root-level access to perform all basic debug operations along with Edge actions such as restart, deactivate, reboot, hard reset, and shutdown. In addition, you can access Linux shell.
    The default value is Basic.
    Note: Only Operator Super Users can modify the default value to Privileged.
    Note: The Next button is activated only when you enter all the mandatory details in each section.
  5. Select the Add another user check box if you wish to create another user, and then select Add User.
    The new user appears in the User Management > Users page.
  6. Select the link to the user to view or modify the details.

API Tokens

You can access the Orchestrator APIs using tokens instead of session-based authentication. As an Operator Superuser, you can manage the API tokens. You can create multiple API tokens for a user.
Note: For Enterprise Read Only users and MSP Business Specialist users, token-based authentication is not activated.
By default, the API Tokens are activated. If you want to deactivate them, go to System Properties in the Operator portal, and set the value of the system property session.options.enableApiTokenAuth as False.
Note: Operator Superuser should manually delete inactive Identity Provider (IdP) users from the Orchestrator to prevent unauthorized access via API Token.

The users can create, revoke, and download the tokens based on their roles.

To manage the API tokens:

  1. In the Operator portal, navigate to Administration > User Management > Users .
  2. Select a user and select Modify or select the link to the username.
  3. Go to the API Tokens section.
    Figure 4. API Tokens
  4. Select New API Token.
    Figure 5. New API Token
  5. In the New Token window, enter a Name and Description for the token, and then choose the Lifetime from the drop-down menu.
  6. Select Save. The new token is displayed in the API Tokens table.
    Initially, the status of the token is displayed as Pending. Once you download it, the status changes to Enabled. When the Lifetime of the token is over, the status changes to Expired.
  7. To download the token, select the token, and then select Download API Token.
  8. To deactivate a token, select the token, and then select Revoke API Token. The status of the token is displayed as Revoked.
  9. Select CSV to download the complete list of API tokens in a .csv file format.
    Note: Only the user who is associated with a token can download it and after downloading, the ID of the token alone is displayed. You can download a token only once. After downloading the token, the user can send it as part of the Authorization Header of the request to access the Orchestrator API.
    The following example shows a sample snippet of the code to access an API. 
    curl -k -H "Authorization: Token <Token>" -X POST https://vco/portal/ -d '{ "id": 1, "jsonrpc": "2.0", "method": "enterprise/getEnterpriseUsers", "params": { "enterpriseId": 1 }}'
    Similarly, you can configure additional properties and create API tokens for Partner Admins, Enterprise Customers, and Partner Customers. For additional information, see:
    • Users topic in the Arista VeloCloud SD-WAN Partner Guide
    • Users topic in the Arista VeloCloud Global Settings Guide
    The following are the other options available in the API Tokens section:
    Table 4. Additional Options
    Option Description
    Search Enter a search term to search for the matching text across the table. Use the advanced search option to narrow down the search results.
    Columns Select the columns to be displayed or hidden on the page.
    Refresh Select to refresh the page to display the most current data.

Roles

The Orchestrator consists of two types of roles.
Note: Starting from the 5.1.0 release, Functional Roles are renamed as Privileges, and Composite Roles are renamed as Roles.
The roles are categorized as follows:
  • Privileges – Privileges are a set of roles relevant to a functionality. A privilege can be tagged to one or more of the following services: SD-WAN and Global Settings. Users require privileges to carry out business processes. For example, a Customer support role in SD-WAN is a privilege required by an SD-WAN user to carry out various support activities. Every service defines such privileges based on its supported business functionality.
  • Roles – The privileges from various categories can be grouped to form a role. By default, the following roles are available for an Operator user:
    Table 5. Operator Roles
    Role SD-WAN Service Cloud Web Security Service Secure Access Service Global Settings Service
    Operator Standard Admin SD-WAN Operator Admin Cloud Web Security Operator Admin Secure Access Operator Admin Global Settings Operator Admin
    Operator Superuser Full Access Full Access Full Access Full Access
    Operator Business SD-WAN Operator Business - - Global Settings Operator Business
    Operator Support SD-WAN Operator Support Cloud Web Security Operator Read Only Secure Access Operator Read Only Global Settings Operator Support

    If required, you can customize the privileges of these roles. For additional information, see Service Permissions.

As an Operator, you can view the list of existing standard roles and their corresponding descriptions. You can add, edit, clone, or delete a new role. However, you cannot edit or delete a default role.

To access the Roles tab:

  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management, and then select the Roles tab.
    The following screen appears:
    Figure 6. Roles tab
  3. On the Roles screen, you can perform the following activities:
    Table 6. Roles Tab- Options and Descriptions
    Option Description
    Add Role Creates a new custom role. For additional information, see Add Role.
    Edit Allows you to edit only the custom roles. You cannot edit the default roles. Also, you cannot edit or view the settings of a Superuser.
    Clone Role Creates a new custom role, by cloning the existing settings from the selected role. You cannot clone the settings of a Superuser.
    Delete Role Deletes the selected role. You cannot delete the default roles. You can delete only custom composite roles. Ensure that you have removed all the users associated with the selected role, before deleting the role.
    Download CSV Downloads the details of the user roles into a file in CSV format.
    Note: You can also access the Edit, Clone Role, and Delete Role options from the vertical ellipsis of the selected Role.
  4. Select the Open icon >> displayed before the Role link, to view additional details about the selected Role, as shown below:
    Figure 7. Role Details
  5. Select the View Role link to view the privileges associated to the selected role for the following services:
    • Global Settings & Administration
    • SD-WAN
  6. The following are the other options available in the Roles tab:
    Table 7. Additional Options
    Option Description
    Search Enter a search term to search for the matching text across the table. Use the advanced search option to narrow down the search results.
    Columns Select the columns to be displayed or hidden on the page.
    Refresh Select to refresh the page to display the most current data.

Add Role

To add a new role for an Operator, perform the following steps:
  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management, and then select the Roles tab.
  3. Select Add Role.
    The following screen appears:
    Figure 8. Add Role
  4. Enter the following details for the new custom role:
    Table 8. Add Role- Options and Descriptions
    Option Description
    Role Details
    Role Name Enter a name for the new role.
    Role Description Enter a description for the role.
    Template Optionally, select an existing role as template from the drop-down list. The privileges of the selected template are assigned to the new role.
    Scope Select Operator, Partner, or Customer as the scope for the new role. The new role appears in all the accounts for the selected user, as a default role. If an Operator creates a role for a Partner, it appears in the Partner's roles' list and can be edited only by an Operator and a Partner user who has the required permissions.
    Role Creation: The options in this section vary depending on the selected Scope.
    Global Settings & Administration These privileges provide access to user management and global settings that are shared across all services. Choosing one of the privileges is mandatory. By default, Global Settings Operator Support is selected for the Operator scope.
    SD-WAN These privileges provide the Operator, Partner, or Enterprise Administrator with different levels of read and/or write access around SD-WAN configuration, monitoring, and diagnostics. You can optionally choose an SD-WAN privilege. The default value is No Privileges.
    Cloud Web Security These privileges provide the Operator, Partner, or Enterprise Administrator with different levels of read and/or write access around Cloud Web Security features. You can optionally choose a Cloud Web Security privilege. The default value is No Privileges.
    Secure Access These privileges provide the Operator, Partner, or Enterprise Administrator with different levels of read and/or write access around Secure Access features. You can optionally choose a Secure Access function privilege. The default value is No Privileges.
    Multi Cloud These privileges provide the Operator, Partner, or Enterprise Administrator with different levels of read and/or write access around Multi Cloud features. You can optionally choose a Multi Cloud function privilege. The default value is No Privileges.
    App Catalog These privileges provide the Operator, Partner, or Enterprise Administrator with different levels of read and/or write access around App Catalog features. You can optionally choose an App Catalog function privilege. The default value is No Privileges.

     

  5. Select Save Changes.
    The new custom role appears in the User Management > Roles page of the user, depending on the selected Scope.
  6. Select the link to the custom role to view the settings.

Service Permissions

Service Permissions allow an Administrator to granularly define actions (Read, Create, Update, and Delete) assigned to each Privilege (such as Cloud Security Service and Customer Segment configuration) within a Privilege Bundle.
Note:
  • Starting from the 5.1.0 release, Role Customization is renamed as Service Permissions.
  • To activate this feature, an Operator must navigate to Global Settings > Customer Configuration > Additional Configuration > Feature Access , and then check the Role Customization check box.

You can customize only the permissions and not the roles. When you customize a permission, the changes would impact the roles associated with it. For additional information, see Roles.

The Service Permissions are applied to the privileges as follows:
  • The customizations done at the Enterprise level override the Partner or Operator level customizations.
  • The customizations done at the Partner level override the Operator level customizations.
  • Only when there are no customizations done at the Partner level or Enterprise level, the customizations made by the Operator are applied globally across all users in the Orchestrator.
Note: For information on user privileges, see List of User Privileges.

To access the Service Permissions tab:

  1. In the Operator Portal, select Administration from the top menu.
  2. From the left menu, select User Management, and then select the Service Permissions tab.
    The following screen appears:
    Figure 9. Service Permissions Tab
  3. On the Service Permissions screen, you can perform the following activities:
    Table 9. Service Permissions tab- Options and Descriptions
    Option Description
    Service Select the service from the drop-down menu. The available services are:
    • All
    • Global Settings
    • SD-WAN

    Custom service permissions, if any, associated with the selected service are displayed. By default, all of the custom service permissions are displayed.
    New Permission Allows you to create a new permission. For additional information, see New Permission.
    Edit Allows you to edit the settings of the selected permission. You can also select the link to the Permission Name to edit the settings.
    Clone Allows you to create a copy of the selected permission.
    Publish Permission Applies the customization available in the selected package to the existing permission. This option modifies the privileges only at the current level. If there are customizations available at the Operator level or a lower level for the same role, then the lower level takes precedence.
    More Allows you to select from the following additional options:
    • Delete: Deletes the selected permission. You cannot delete a permission if it is already in use.
      Note: A permission can only be deleted if it is in a draft mode. The Delete option is deactivated for a published permission. If you want to delete a published permission, you must reset the permission to system default, which changes it to draft mode and activates the Delete option for the permission.
    • Download JSON: Downloads the list of permissions into a file in JSON format.
    • Upload Permission: Allows you to upload a JSON file of a customized permission.
    • Reset to System Default: Allows you to reset the current published permissions to default settings. Only the permissions applied to the privileges in the current level (Operator, Partner, or Enterprise) of the SASE Orchestrator are reset to the default settings. If Operators or Customers have customized their privileges in the Partner or Enterprise level in the Orchestrator, those settings remain the same.

     

  4. The following are the other options available in the Service Permissions tab:
    Table 10. Additional Options
    Option Description
    Columns Select the columns to be displayed or hidden on the page.
    Note: The Role Associated column displays the Roles using the same Privilege Bundle.
    Refresh Select to refresh the page to display the most current data.
    Note: Service Permissions are version dependent, and a service permission created on an Orchestrator using an earlier software release will not be compatible with an Orchestrator using a later release. For example, a service permission created on an Orchestrator that is running Release 3.4.x does not work properly if the Orchestrator is upgraded to a 4.x Release. Also, a service permission created on an Orchestrator running Release 3.4.x does not work properly when the Orchestrator is upgraded to 4.x.x Release. In such cases, the user must review and recreate the service permission for the newer release to ensure proper enforcement of all roles.

New Permission

You can customize the privileges and apply them to the existing permission in the VeloCloud Orchestrator.

To add a new permission, perform the following steps:

  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management, and then select the Service Permissions tab.
  3. Select New Permission.
    The following screen appears:
    Figure 10. New Permission
  4. Enter the following details to create a new permission:
    Table 11. New Permission- Options and Descriptions
    Option Description
    Name Enter an appropriate name for the permission.
    Description Enter a description. This field is optional.
    Scope Select Operator, Partner, or Enterprise as the scope. An Operator can apply the permissions for Operators, Partners, and Customers.
    Service Select a service from the drop-down menu. The available services are:
    • Global Settings
    • SD-WAN
    • Edge Compute
    Privilege Bundle Select a privilege bundle from the drop-down menu. The privileges are populated depending on the selected Service.
    Privileges Displays the list of privileges based on the selected Privilege Bundle. You can edit only those privileges that are eligible for customization.
    Note: Operator Superuser role cannot be customized.
  5. Select Download CSV to download the list of all privileges, their description, and associated actions, into a file in CSV format.
  6. Select Save to save the new permission. Select Save and Apply to save and publish the permission.
    Note: The Save and Save and Apply buttons are activated only after you modify the permissions.
    The new permission is displayed on the Service Permissions page.

List of User Privileges

This section lists all the privileges available in the Operator portal.

The columns in the table indicate the following:
  • Allow Privilege – Do the privileges have allow access?
  • Deny Privilege – Do the privileges have deny access?
  • Customizable – Is the privilege available for customization in the Service Permissions tab?
Table 12. List of User Privileges
Feature Name of the Privilege Description Allow Privilege Deny Privilege Customizable
Manage Customers Create Customer Grants ability to view and manage Enterprise Customers as an Operator or a Partner Yes No No
  Read Customer
  Update Customer Yes Yes
  Delete Customer No No
  Manage Customer
Manage Partners Create Partner Grants ability to view and manage Partners Yes No No
  Read Partner
  Update Partner
  Delete Partner
  Manage Partner
Software Images Create Software Package Grants access to upload and assign Edge Software Images and Application Maps Yes Yes Yes
  Read Software Package
  Update Software Package
  Delete Software Package
  Manage Software Package
System Properties Create System Property Grants access to view and manage System Properties Yes Yes No
  Read System Property Yes
  Update System Property No
  Delete System Property No
  Manage System Property Yes
  Edit Restricted System Properties Controls the ability of user to edit restricted system properties Yes No No
Operator Events Create Operator Event Grants ability to view Operator events Yes Yes Yes
  Read Operator Event
  Update Operator Event
  Delete Operator Event
  Manage Operator Event
Operator Profiles Create Operator Profile Grants ability to view and manage Operator profiles Yes Yes Yes
  Read Operator Profile
  Update Operator Profile
  Delete Operator Profile
  Manage Operator Profile
  View Tab Operator Profile Controls ability of the user to view and configure within the Operator profile menu No Yes Yes
Operator Users Create Operator User Grants ability to view and manage Operator administrative users Yes Yes No
  Read Operator User Yes
  Update Operator User No
  Delete Operator User No
  Manage Operator User Yes
Operator Users > API Tokens Create Operator Token Grants ability to view and manage the operator Authentication Tokens Yes No No
  Read Operator Token
  Update Operator Token
  Delete Operator Token
  Manage Operator Token
Gateway Pools Gateways Gateway Diagnostic bundles Create Gateway Grants ability to view and manage Gateway pools and Gateways as an Operator or a Partner Yes Yes Yes
Read Gateway
Update Gateway
Delete Gateway
Manage Gateway
View Tab Gateway List Controls the ability of user to view the list of Gateways No Yes Yes
Gateways > New Gateway Create Operator PKI Grants ability to view and manage Operator level PKI configuration including Gateway certificates and certificate authority Yes Yes No
Gateway > Gateway Authentication Mode Read Operator PKI Yes
  Update Operator PKI No
  Manage Operator PKI Yes
Gateway Diagnostic Bundles > Download Diagnostic Bundles Download Gateway Diagnostics Grants ability to download Gateway Diagnostics No Yes Yes
Application Maps Create Software Package Grants access to upload and assign Edge software images and Application Maps Yes Yes Yes
  Read Software Package
  Update Software Package
  Delete Software Package
  Manage Software Package
Service Permissions Create Service Permissions Package Grants access to manage Service Permissions packages Yes No No
  Read Service Permissions Package
  Update Service Permissions Package
  Delete Service Permissions Package
  Manage Service Permissions Package
Edge Licensing Create License Grants ability to view and manage Edge licensing Yes No No
  Read License Yes Yes
  Update License
  Delete License No No
  Manage License
CA Summary > Gateway Certificates > Revoke Certificate Read Operator PKI Grants ability to view and manage operator level PKI configuration including Gateway certificates and certificate authority Yes Yes Yes
  Delete Operator PKI No
  Manage Operator PKI Yes
  Read Customer PKI Grants ability to view and manage Enterprise PKI settings Yes No No
  Delete Customer PKI
  Manage Customer PKI
Orchestrator Authentication > Operator Authentication Create Operator Authentication Grants ability to view and manage Operator authentication mode, like SSO, RADIUS, or Native Yes Yes Yes
  Read Operator Authentication
  Update Operator Authentication
  Delete Operator Authentication
  Manage Operator Authentication
Orchestrator Authentication > Enterprise Authentication Create Customer Authentication Grants ability to view and manage Customer authentication mode, like RADIUS or Native Yes Yes Yes
  Read Customer Authentication
  Update Customer Authentication
  Delete Customer Authentication
  Manage Customer Authentication
Replication Create Replication Grants access to view and configure Orchestrator disaster recovery Yes Yes No
  Read Replication Yes
  Update Replication No
  Delete Replication
  Manage Replication Yes
Orchestrator Diagnostics > Diagnostic Bundles Create Orchestrator Diagnostics Grants access to request and view Orchestrator diagnostic bundles Yes Yes Yes
Orchestrator Diagnostics > Database Statistics Read Orchestrator Diagnostics
  Update Orchestrator Diagnostics
  Delete Orchestrator Diagnostics
  Manage Orchestrator Diagnostics
Orchestrator Upgrade for Standalone Create Software Package Grants access to upload and assign Edge software images and Application Maps Yes Yes Yes
  Read Software Package
  Update Software Package
  Delete Software Package
  Manage Software Package
Orchestrator Upgrade for DR Setup Create Replication Grants access to view and configure Orchestrator disaster recovery Yes Yes No
  Read Replication Yes
  Update Replication No
  Delete Replication
  Manage Replication Yes
User Agreements Create User Agreement Grants access to configure the customer user agreement Yes No No
  Read User Agreement
  Update User Agreement
  Delete User Agreement
  Manage User Agreement
Orchestrator Owners Manage Orchestrators Edge Inventory Create Edge Inventory Grants ability to view and manage Edge inventory as needed for Redirect configuration Yes No No
Read Edge Inventory
Update Edge Inventory
Delete Edge Inventory
Manage Edge Inventory

When the corresponding user privilege is denied, the Orchestrator window displays the 404 resource not found error.

The following table provides a list of customizable feature privileges:
Table 13. List of Customizable Privileges
Navigation Path in the Enterprise Portal Name of the Tab Name of the Privilege Description
Configure > Edges > Select Edge Overview Assign Edge Profile Grants ability to assign a Profile to Edges
Configure > Edges > Select Edge Firewall Configure Edge Firewall Logging Grants ability to configure Edge level firewall logging
Configure > Profiles > Select Profile Firewall Configure Profile Firewall Logging Grants ability to configure Profile level firewall logging
Diagnostics > Remote Actions Select Edge > Deactivate Deactivate Edge Grants ability to reset the device configuration to its factory default state
Global Settings > Enterprise Settings > Information Privacy Settings > SD-WAN PCI Enforce PCI Compliance Deny PCI Operations Denies access to sensitive Customer data including PCAPs, etc. on the Edges and Gateways, for all users including Arista Support
Diagnostics > Diagnostic Bundles Select Edge > Download Bundle Download Edge Diagnostics Grants ability to download Edge Diagnostics
Gateway Management > Diagnostic Bundles Select Gateway > Download Bundle Download Gateway Diagnostics Grants ability to download Gateway Diagnostics
Configure > Profiles Duplicate Duplicate Customer Profile Grants ability to edit duplicate customer level Profiles
Configure > Segments / Configure > Profiles > Configure > Edges Segments drop-down menu Edit Tab Segments Grants ability to edit within the Segments tab
Configure > Edges > Select Edge Device Enable HA Cluster Grants ability to configure HA Clustering
Configure > Edges > Select Edge Device Enable HA Active/Standby Pair Grants ability to configure active/standby HA
Configure > Edges > Select Edge Device Enable HA VRRP Pair Grants ability to configure VRRP HA
Diagnostics > Remote Diagnostics Clear ARP Cache Remote Clear ARP Cache Grants ability to clear the ARP cache for a given interface
Diagnostics > Remote Diagnostics > Gateway Cloud Traffic Routing (drop-down menu) Remote Cloud Traffic Routing Grants ability to route cloud traffic remotely
Diagnostics > Remote Diagnostics DNS/DHCP Service Restart Remote DNS/DHCP Restart Grants ability to restart the DNS/DHCP service
Diagnostics > Remote Diagnostics Flush Flows Remote Flush Flows Grants ability to flush the Flow table, causing user traffic to be re-classified
Diagnostics > Remote Diagnostics Flush NAT Remote Flush NAT Grants ability to flush the NAT table
Diagnostics > Remote Diagnostics > LTE SIM Switchover LTE Switch SIM Slot
Note: This is for 610-LTE and 710 5G devices only.
 Remote LTE Switch SIM Slot Grants ability to activate the SIM Switchover feature. After the test is successful, you can check the status from Monitor > Edges > Overview tab
Diagnostics > Remote Diagnostics List Paths Remote List Paths Grants ability to view the list of active paths between local WAN links and each peer
Diagnostics > Remote Diagnostics List current IKE Child SAs Remote List current IKE Child SAs Grants ability to use filters to view the exact Child SAs you want to see
Diagnostics > Remote Diagnostics List current IKE SAs Remote List Current IKE SAs Grants ability to use filters to view the exact SAs you want to see
Diagnostics > Remote Diagnostics MIBs for Edge Remote MIBS for Edge Grants ability to dump Edge MIBs
Diagnostics > Remote Diagnostics NAT Table Dump Remote NAT Table Dump Grants ability to view the contents of the NAT table
Diagnostics > Remote Diagnostics Select Edge > Rebalance Hub Cluster Remote Rebalance Hub Cluster Grants ability to either redistribute Spokes in Hub Cluster or redistribute Spokes excluding this Hub
Diagnostics > Remote Diagnostics Select Edge (with SFP module) > Reset SFP Firmware Configuration Remote Reset SFP Firmware Configuration Grants ability to reset the SFP Firmware Configuration
Diagnostics > Remote Actions Reset USB Modem Remote Reset USB Modem Grants ability to execute the Edge USB modem reset remote action
Diagnostics > Remote Diagnostics Scan for Wi-Fi Access Points Remote Scan for Wi-Fi Access Points Grants ability to scan the Wi-Fi functionality for the VeloCloud Edge
Diagnostics > Remote Diagnostics System Information Remote System Information Grants ability to view system information such as system load, recent WAN stability statistics, monitoring services
Diagnostics > Remote Diagnostics VPN Test Remote VPN Test Grants ability to execute the Edge VPN test remote action
Diagnostics > Remote Diagnostics WAN Link Bandwidth Test Remote WAN link Bandwidth Test Grants ability to re-test the bandwidth of a WAN link
Diagnostics > Remote Actions Select Edge > Shutdown Shutdown Edge Grants ability to execute the Edge shutdown remote action
Service Settings > Alerts & Notifications Notifications Email/SMS Update Customer SMS Alert Grants ability to configure SMS alerts at the customer level
Monitor > Edges > Select Edge Top Sources View Edge Sources Grants ability to view Monitor Edge Sources tab
Monitor > Firewall Firewall Logging View Firewall Logs Grants ability to view collected firewall logs
Monitor > Edges > Select Edge Top Sources View Flow Stats Grants ability to view collected flow statistics
Monitor > Firewall Logs Firewall Logs View Profile Firewall Logging Grants ability to view the details of firewall logs originating from VeloCloud Edges
Configure > Profiles Firewall View Stateful Firewall Grants ability to view collected flow statistics
Configure > Profiles Firewall tab > Configure Firewall > Syslog Forwarding View Syslog Forwarding Grants ability to view logs that are forwarded to a configured syslog collector
Operator portal > Gateway Management Gateways View Tab Gateway List Grants ability to view the Gateway list tab
Operator portal > Administration Operator Profiles View Tab Operator Profile Grants ability to view and configure settings within the Operator Profile menu tab
Monitor > Edges > Select Edge Top Sources View User Identifiable Flow Stats Grants ability to view potentially user identifiable flow source attributes

Authentication

The Authentication feature allows you to set the authentication modes for both, Operators and Enterprise users. You can also view the existing API tokens.

To access the Authentication tab:

  1. In the Operator portal, select Administration from the top menu.
  2. From the left menu, select User Management, and then select the Authentication tab.
    The following screen appears:
    Figure 11. Authentication Tab
  3. API Tokens: You can access the Orchestrator APIs using token-based authentication, irrespective of the authentication mode. Operator Administrators with right permissions can view the API tokens issued to Orchestrator users, including tokens issued to the Partner and Customer users. If required, an Operator Administrator can revoke the API tokens.

    By default, the API Tokens are activated. If you want to deactivate them, go to Orchestrator > System Properties , and set the value of the system property session.options.enableApiTokenAuth as False.

    Note: Operator Superuser should manually delete inactive Identity Provider (IdP) users from the Orchestrator to prevent unauthorized access via API Token.
    The following are the options available in this section:
    Table 14. API Tokens- Options and Descriptions
    Option Description
    Search Enter a search term to search for the matching text across the table. Use the advanced search option to narrow down the search results.
    Revoke API Token Select the token and select this option to revoke it. Only an Operator Super User or the user associated with an API token can revoke the token.
    CSV Select this option to download the complete list of API tokens in a .csv file format.
    Columns Select the columns to be displayed or hidden on the page.
    Refresh Select to refresh the page to display the most current data.

    As an Operator Superuser, you can manage the API tokens for Enterprise users. For information on creating and downloading API tokens, see API Tokens.

  4. Operator Authentication / Enterprise Authentication: Select one of the following Authentication modes:
    • Local: This is the default option and does not require any additional configuration.
    • Single Sign-On: Operator users with Superuser permission can set up and configure Single Sign On (SSO) in the Orchestrator. Single Sign-On (SSO) is a session and user authentication service that allows users to log in to multiple applications and websites with one set of credentials. Integrating an SSO service with the Orchestrator enables the Orchestrator to authenticate users from OpenID Connect (OIDC)-based Identity Providers (IdPs).
      Prerequisites:
      • Ensure that you have the Operator Superuser permission.
      • Before setting up the SSO authentication in SASE Orchestrator, make sure that you have set up Users, Service Permissions, and OpenID connect (OIDC) application for SASE Orchestrator in your preferred identity provider’s website.
      Note:
      • Single Sign-On mode is available only for Operator Authentication in the Operator portal.
      • Token-based authentication is deactivated for SSO users.
      • SSO integration at the Operator management level of a Arista hosted Orchestrator is reserved for the VeloCloud SD-WAN TechOPS Operators. Partners with Operator level access of a hosted Orchestrator do not have the option to integrate to an SSO service.
      To enable Single Sign On (SSO) for VeloCloud Orchestrator, you must enter the Orchestrator application details into the Identity Provider (IdP). Select each of the following links for step-by-step instructions to configure the following supported IdPs:
      You can configure the following options when you select the Authentication Mode as Single Sign-on.
      Figure 12. Single Sign-on Authentication

       

      Table 15. Single Sign-on Authentication- Options and Descriptions
      Option Description
      Identity Provider Template From the drop-down menu, select your preferred Identity Provider (IdP) that you have configured for Single Sign On. This pre-populates fields specific to your IdP.
      Note: You can also manually configure your own IdPs by selecting Others from the drop-down menu.
      OIDC well-known config URL Enter the OpenID Connect (OIDC) configuration URL for your IdP. For example, the URL format for Okta will be: https://{oauth-provider-url}/.well-known/openid-configuration.
      Issuer This field is auto-populated based on your selected IdP.
      Authorization Endpoint This field is auto-populated based on your selected IdP.
      Token Endpoint This field is auto-populated based on your selected IdP.
      JSON Web KeySet URI This field is auto-populated based on your selected IdP.
      User Information Endpoint This field is auto-populated based on your selected IdP.
      Client ID Enter the client identifier provided by your IdP.
      Client Secret Enter the client secret code provided by your IdP, that is used by the client to exchange an authorization code for a token.
      Scopes This field is auto-populated based on your selected IdP.
      Role Type Select one of the following two options:
      • Use default role
      • Use identity provider roles
      Role Attribute Enter the name of the attribute set in the IdP to return roles.
      Operator Role Map Map the IdP-provided roles to each of the Operator user roles.

      Select Update to save the entered values. The SSO authentication setup is complete in the Orchestrator.

    • RADIUS: Remote Authentication Dial-In User Service (RADIUS) is a client-server protocol that enables remote access servers to communicate with a central server. RADIUS authentication provides a centralized management for users. You can configure the Orchestrator Authentication in RADIUS mode, so that the Operator and Enterprise Customers log into the portals using the RADIUS servers. Enter appropriate details in the following fields:
      Figure 13. RADIUS Authentication
      • You can edit the Protocol value only in the System Properties. Navigate to Orchestrator > System Properties , and edit the protocol in the Value field of the system property vco.operator.authentication.radius.
      • The Operator Domain field is available only for Operators.
      • In the Operator Role Map / Enterprise Role Map section, map the RADIUS server attributes to each of the Operator or Enterprise user roles. This role mapping is used to determine the role the users would be assigned when they login to the Orchestrator using the RADIUS server for the first time.
      • Select Update to save the entered values.
  5. SSH Keys: You can create only one SSH Key per user. Select the User Information icon located at the top right of the screen, and then select My Account > SSH Keys to create an SSH Key.

    As an Operator, you can also revoke an SSH Key.

    Select the Refresh option to refresh the section to display the most current data.

    For additional information, see Configure User Account Details.

  6. Session Limits:
    Note: To view this section, an Operator user must navigate to Orchestrator > System Properties , and set the value of the system property session.options.enableSessionTracking to True.

    The following are the options available in this section:

    Table 16. Session Limits - Options and Descriptions
    Option Description
    Concurrent logins Allows you to set a limit on concurrent logins per user. By default, Unlimited is selected, indicating that unlimited concurrent logins are allowed for the user.
    Session limits for each role Allows you to set a limit on the number of concurrent sessions based on user role. By default, Unlimited is selected, indicating that unlimited sessions are allowed for the role.
    Note: The roles that are already created by the Operator in the Roles tab, are displayed in this section.

     

  7. Select Update to save the selected values.

Configure Azure Active Directory for Single Sign On

Ensure you have an Azure AD account to sign in.
To set up an OpenID Connect (OIDC)-based application in Microsoft Azure Active Directory (Azure AD) for Single Sign On (SSO), perform the following steps.
  1. Log in to your Microsoft Azure account as an Admin user.
    The Microsoft Azure home screen appears.
  2. To create a new application:
    1. Search and select the Azure Active Directory service.
      Figure 14. Azure Active Directory
    2. Go to App registration > New registration .
      The Register an application screen appears.
      Figure 15. Register an Application
    3. In the Name field, enter the name for your Orchestrator application.
    4. In the Redirect URL field, enter the redirect URL that your SASE Orchestrator application uses as the callback endpoint.
    5. In the Orchestrator application, at the bottom of the Configure Authentication screen, you can find the redirect URL link. Ideally, the Orchestrator redirect URL will be in this format: https://<Orchestrator URL>/login/ssologin/openidCallback.
    6. Select Register.
      Your Orchestrator application will be registered and displayed in the All applications and Owned applications tabs. Make sure to note down the Client ID/Application ID to be used during the SSO configuration in the Orchestrator.
    7. Select Endpoints and copy the well-known OIDC configuration URL to be used during the SSO configuration in the Orchestrator.
    8. To create a client secret for your Orchestrator application, on the Owned applications tab, select your Orchestrator application.
    9. Go to Certificates & secrets > New client secret .
      The Add a client secret screen appears.
      Figure 16. Add a Client Secret
    10. Provide details such as description and expiry value for the secret and select Add.
      The client secret is created for the application. Note down the new client secret value to be used during the SSO configuration in the Orchestrator.
    11. To configure permissions for your SASE Orchestrator application, select your SASE Orchestrator application and go to API permissions > Add a permission .
      The Request API permissions screen appears.
      Figure 17. Request API Permissions
    12. Select Microsoft Graph and select Application permissions as the type of permission for your application.
    13. Under Select permissions, from the Directory drop-down menu, select Directory.Read.All and from the User drop-down menu, select User.Read.All.
    14. Select Add permissions.
    15. To add and save roles in the manifest, select your Orchestrator application and from the application Overview screen, select Manifest. A web-based manifest editor opens, allowing you to edit the manifest within the portal. Optionally, you can select Download to edit the manifest locally, and then use Upload to reapply it to your application.
      Figure 18. Manifest
    16. In the manifest, search for the appRoles array and add one or more role objects as shown in the following example and select Save.
      Note: The value property from appRoles must be added to the Identity Provider Role Name column of the Role Map table, located in the Authentication tab, in order to map the roles correctly.

      Sample role objects:

      { "allowedMemberTypes": [ "User" ], "description": "Standard Administrator who will have sufficient privilege to manage resource", "displayName": "Standard Admin", "id": "18fcaa1a-853f-426d-9a25-ddd7ca7145c1", "isEnabled": true, "lang": null, "origin": "Application", "value": "standard" }, { "allowedMemberTypes": [ "User" ], "description": "Super Admin who will have the full privilege on SASE Orchestrator", "displayName": "Super Admin", "id": "cd1d0438-56c8-4c22-adc5-2dcfbf6dee75", "isEnabled": true, "lang": null, "origin": "Application", "value": "superuser" }
      Note: Make sure to set id to a newly generated Global Unique Identifier (GUID) value. You can generate GUIDs online using web-based tools (for example, https://www.guidgen.com/), or by running the following commands:
      • Linux/OSX- uuidgen
      • Windows- powershell [guid]::NewGuid()
      Figure 19. Manifest

      Roles are manually set up in the Orchestrator, and must match the ones configured in the Microsoft Azure portal.

      Figure 20. App Roles
  3. To assign groups and users to your Orchestrator application:
    1. Go to Azure Active Directory > Enterprise applications .
    2. Search and select your Orchestrator application.
    3. Select Users and groups and assign users and groups to the application.
    4. Select Submit.
      You have completed setting up an OIDC-based application in Azure AD for SSO.
Configure Single Sign On in the Orchestrator.

Configure Okta for Single Sign On

Ensure you have an Okta account to sign in.
To support OpenID Connect (OIDC)-based Single Sign On (SSO) from Okta, you must first set up an application in Okta. To set up an OIDC-based application in Okta for SSO, perform the steps on this procedure.
  1. Log in to your Okta account as an Admin user.
    The Okta home screen appears.
    Note: If you are in the Developer Console view, then you must switch to the Classic UI view by selecting Classic UI from the Developer Console drop-down list.
  2. To create a new application:
    1. In the upper navigation bar, select Applications > Add Application .
      The Add Application screen appears.
      Figure 21. Add Application
    2. Select Create New App.
      The Create a New Application Integration dialog box appears.
    3. From the Platform drop-drop menu, select Web.
    4. Select OpenID Connect as the Sign on method and select Create.
      The Create OpenID Connect Integration screen appears.
      Figure 22. Create OpenID Connect Integration
    5. Under the General Settings area, in the Application name text box, enter the name for your application.
    6. Under the CONFIGURE OPENID CONNECT area, in the Login redirect URIs text box, enter the redirect URL that your SASE Orchestrator application uses as the callback endpoint.
      In the Orchestrator application, at the bottom of the Configure Authentication screen, you can find the redirect URL link. Ideally, the Orchestrator redirect URL will be in this format: https://<Orchestrator URL>/login/ssologin/openidCallback.
    7. Select Save.
      The newly created application page appears.
    8. On the General tab, select Edit and select Refresh Token for Allowed grant types, and select Save. Note down the Client Credentials (Client ID and Client Secret) to be used during the SSO configuration in the Orchestrator.
      Figure 23. General Settings
    9. Select the Sign On tab and under the OpenID Connect ID Token area, select Edit.
    10. From the Groups claim type drop-down menu, select Expression. By default, Groups claim type is set to Filter.
    11. In the Groups claim expression text box, enter the claim name that will be used in the token, and an Okta input expression statement that evaluates the token.
    12. Select Save.
      The application is setup in IDP. You can assign user groups and users to your Orchestrator application.
      Figure 24. Sign-On tab
  3. To assign groups and users to your Orchestrator application:
    1. Go to Application > Applications and select your Orchestrator application link.
    2. On the Assignments tab, from the Assign drop-down menu, select Assign to Groups or Assign to People.
      The Assign <Application Name> to Groups or Assign <Application Name> to People dialog box appears.
    3. Select Assign next to available user groups or users you want to assign the Orchestrator application and select Done.
      The users or user groups assigned to the Orchestrator application will be displayed.
      Figure 25. Assignments Tab

      You have completed setting up an OIDC-based application in Okta for SSO.

Configure Single Sign On in the Orchestrator.

Configure OneLogin for Single Sign On

Ensure you have an OneLogin account to sign in.
To set up an OpenID Connect (OIDC)-based application in OneLogin for Single Sign On (SSO), perform the steps below:
  1. Log in to your OneLogin account as an Admin user.
    The OneLogin home screen appears.
  2. To create a new application:
    1. In the upper navigation bar, select Apps > Add Apps .
    2. In the Find Applications text box, search for “OpenId Connect” or “oidc” and then select the OpenId Connect (OIDC) app.
      The Add OpenId Connect (OIDC) screen appears.
      Figure 26. Add OpenId Connect (OIDC)
    3. In the Display Name text box, enter the name for your application and select Save.
    4. On the Configuration tab, enter the Login URL (auto-login URL for SSO) and the Redirect URI that Orchestrator uses as the callback endpoint, and select Save.
      • Login URL- The login URL will be in this format: https://<Orchestrator URL>/<Domain>/ login/doEnterpriseSsoLogin. Where, <Domain> is the domain name of your Enterprise that you must have already set up to enable SSO authentication for the Orchestrator. You can get the Domain name from the Enterprise portal > Administration > System Settings > General Information page.
      • Redirect URI's- The Orchestrator redirect URL will be in this format: https://<Orchestrator URL>/login/ssologin/openidCallback. In the Orchestrator application, at the bottom of the Authentication screen, you can find the redirect URL link.
        Figure 27. Application Details
    5. On the Parameters tab, under OpenId Connect (OIDC), double select Groups.
      The Edit Field Groups popup appears.
      Figure 28. Edit Field Groups
    6. Configure User Roles with value “--No transform--(Single value output)” to be sent in groups attribute and select Save.
    7. On the SSO tab, from the Application Type drop-down menu, select Web.
    8. From the Authentication Method drop-down menu, select POST as the Token Endpoint and select Save. Also, note down the Client Credentials (Client ID and Client Secret) to be used during the SSO configuration in the Orchestrator.
      Figure 29. SSO Tab
    9. On the Access tab, choose the roles that will be allowed to login and select Save.
      Figure 30. Access Tab
  3. To add roles and users to your Orchestrator application:
    1. Select Users > Users and select a user.
    2. On the Application tab, from the Roles drop-down menu, on the left, select a role to be mapped to the user.
    3. Select Save Users.
      You have completed setting up an OIDC-based application in OneLogin for SSO.
Configure Single Sign On in the Orchestrator.

Configure PingIdentity for Single Sign On

Ensure you have a PingOne account to sign in.
Note: Currently, the Orchestrator supports PingOne as the Identity Partner (IDP); however, any PingIdentity product supporting OIDC can be easily configured.
To set up an OpenID Connect (OIDC)-based application in PingIdentity for Single Sign On (SSO), perform the steps on this procedure.
  1. Log in to your PingOne account as an Admin user.
    The PingOne home screen appears.
  2. To create a new application:
    1. In the upper navigation bar, select My Applications.
      Figure 31. My Applications
    2. On the My Applications tab, select OIDC and then select Add Application.
      The Add OIDC Application pop-up window appears.
      Figure 32. Add OIDC Application
    3. Provide basic details such as name, short description, and category for the application and select Next.
    4. Under AUTHORIZATION SETTINGS, select Authorization Code as the allowed grant types and select Next. Also, note down the Discovery URL and Client Credentials (Client ID and Client Secret) to be used during the SSO configuration in the Orchestrator.
    5. Under SSO FLOW AND AUTHENTICATION SETTINGS, provide valid values for Start SSO URL and Redirect URL and select Next.
      In the Orchestrator application, at the bottom of the Configure Authentication screen, you can find the redirect URL link. Ideally, the Orchestrator redirect URL will be in this format: https://<Orchestrator URL>/login/ssologin/openidCallback. The Start SSO URL will be in this format: https://<Orchestrator URL>/<domain name>/login/doEnterpriseSsoLogin.
    6. Under DEFAULT USER PROFILE ATTRIBUTE CONTRACT, select Add Attribute to add additional user profile attributes.
    7. In the Attribute Name text box, enter group_membership and then select the Required check box, and select Next.
      Note: The group_membership attribute is required to retrieve roles from PingOne.
    8. Under CONNECT SCOPES, select the scopes that can be requested for your Orchestrator application during authentication and select Next.
    9. Under Attribute Mapping, map your identity repository attributes to the claims available to your Orchestrator application.
      Note: The minimum required mappings for the integration to work are email, given_name, family_name, phone_number, sub, and group_membership (mapped to memberOf).
    10. Under Group Access, select all user groups that should have access to your SASE Orchestrator application and select Done.
      The application will be added to your account and will be available in the My Application screen. You have completed setting up an OIDC-based application in PingOne for SSO.
Configure Single Sign On in the Orchestrator.