Skip to content

Configuration

Roles with access

Only administrators have access to this feature.

To go to the Config section, press the button

To go to the "Config" section, press the button

For the following sections we will have to press the corresponding button.

Scheduler

To access this section we will have to press the first button of the dropdown menu

In this section we can differentiate between two subsections:

  • Desktops timeouts: Maximum time a desktop can be on.
  • Job scheduler: Task Scheduler.

Desktop timeout

In this section, you can schedule the maximum time that desktops can remain powered on. The schedule can be applied by role, category, groups, or individual users.

To do a new schedule, we will have to press and we will get the following modal:

Where we can see:

  • Name: The name this schedule will have.
  • Description: Minim explanation (optional).
  • Kind: Action to be performed on desktops. In this case, we only have "shutdown" available.
  • Priority: Schedule priority. Higher number, higher priority.
  • Max (min): Maximum minutes until this schedule is applied.
  • Warning (min): Minutes that must pass to send a warning about what the schedule will be carried out.
  • Danger (min): Minutes that have to pass to send a second notice of what the schedule will be carried out.
  • Allows: Filters to assign who this schedule is directed to. They can be combined, so that they can be more selective.

Once configured, we will press Create timeout and we will be added the schedule to the list.

Task Scheduler

In this section you can plan a task, it can be a backup, a desktop deletion, etc.

We will be able to see a table, where they show us the tasks we have planned:

  • Name: Assignment name.
  • Kind: Task Schedule.
    • Interval: Run the task every X time, which we will assign.
    • Date: Executes the task on an assigned day.
    • Cron: Run the task every X time, which we will assign.
  • Next run: Next date the task will be executed.

In order to create a task we will have to press and we will get the following modal:

  • Type: Task schedule.
    • Interval: Run the task every X time, which we will assign.
    • Date: Executes the task on an assigned day.
    • Cron: Run the task every X time, which we will assign.
  • Hour: Specifies the time.
  • Minute: Specifies the minute.
  • Action: Action to be performed:
    • Check ephimeral status: Verify the status of temporary desktops.
    • Consolidate consumptions: Calculate usage
    • Deployment qmp notification: Notification within deployment as system notification.
    • Domain qmp notification: Notification on the desktop as system notification.
    • GPU desktops destroy: Erase desktops that have assigned GPUs.
    • GPU desktops notify: Notify desktops that have assigned GPUs.
    • GPU profile set: Put a specific profile on a GPU.
    • Logs desktops old entries action delete: Erase old desktop records.
    • Logs users old entries action delete: Erase old user logs.
    • Queues old tasks action delete: Delete old queued tasks.
    • Recycle bin old entries action delete: Erase old entries from the recycle bin.
    • Retry failed tasks: Retry failed tasks.
    • Stop domains without viewer: Stop domains without active viewers.
    • Stop shutting down desktops: Stop turning off desktops.

Viewers

To access this section we will have to press the second button of the dropdown menu

In this section we can see the options of the viewers of the platform:

There are three available configurations. Some parameters are fixed (not editable) and, if accidentally modified, could cause the viewer to stop working. These are indicated in the “Fixed” column. On the other hand, there are parameters that can be configured manually or left with their default value. These are represented in the “Default” and “Custom” columns, respectively.

  • Using the button we can edit these settings.
  • Through the button we can leave the default settings again.

Authentication

To access this section we will have to press the third button of the dropdown menu

It consists of two sections:

  • Authentication: Where we can see which authentication methods have been activated.
  • Migration exemptions: In this section are configured the parameters that determine which users are required to perform the account migration.

Authentication

In this section we can find all the authentication methods that we have available on the platform. And the actions that are allowed or not. Within the platform we offer four login methods:

  • Local: Users who have been created directly on the platform and do not use a third-party method to log in.
  • Google: Sign in with your Google account.
  • SAML: Log in to an application using an external account (such as the corporate one) through an identity provider. This system allows for secure centralized authentication without creating new credentials.
  • LDAP: Log in using a centralized directory of users, such as a corporate network. This system allows you to validate credentials against an LDAP server.

Using the button we can edit the configuration of each login method. The following modal will appear:

Where we can modify the following parameters:

  • Migration: We may or may not activate the import or export of users.
    • Migration settings: We can determine the action that is done with the source user of the migration once done.

    • Add status bar notification: It will add a notification to our user. We can edit this notification.

      • Notification template: It will redirect us to the notifications section where we can edit the message that will be displayed.
      • Notification level: will change the color of the notification according to the degree we want to give it.
        • Info: Box in blue.
        • Warning: Box in yellow.
        • Danger: Box in red.

Once the parameters are edited, press the Update button and the changes will be applied.

Migration exemptions

In this section, you can define which users will be excluded from the migration process. That is, if an account migration is applied, only the users selected here will not be required to perform it.

In order to determine who will not migrate, we have different buttons where we can add roles, categories, groups and users.

All you have to do is write the name we want to exclude.

System

To access this section we will have to press the fourth button of the dropdown menu

Maintenance mode

Maintenance mode disable the web interface for users with manager, advanced and user roles.

The system administrator can create a file called /opt/isard/config/maintenance to switch to maintenance mode at startup. The file is deleted once the system changes to maintenance mode.

To enable and disable this function, check the box:

Once the box is checked, when users try to log in to their account, a maintenance message will appear.

The message displayed on the maintenance page can be edited in the Maintenance text section by pressing the edit icon. We will have the following modal where we can edit it:

Login

To access this section we will have to press the last button of the dropdown menu

In this section we can edit the login page in two ways:

  • Enable left login notification: Activates a notification or notice, depending on the content, that is seen when you log in from any account.
  • Enable right login notification: Where we can add a notification to the right side of the login page.

To edit it, press the edit icon and the following modal will appear:

We can define the type of notification, as well as its title and body. It's also possible to add text with a link to a URL and customize the box and background colors according to our preferences.