Skip to content

Guide

All workloads are run unisolated in the operating system.

Altair SLC Hub users map to operating system users. This should be consistent across the Altair SLC Hub and worker nodes.

For users created locally, the information to map the local Altair SLC Hub user to the OS user must be entered manually.

For users synced from an LDAP server, the OS user linked to the synced LDAP user can also be synced from the LDAP server.

Altair SLC Hub will run these workloads using the operating system permissions appropriate to the user that started the workload. That is, it will impersonate the end user.

Each user account in Altair SLC Hub has two properties, one that defines the operating system user to use when running workloads on Windows and one that defines the operating system to use when running workloads on Linux. For Hub user accounts that are synchronized from LDAP, these properties are populated from the appropriate fields in the LDAP entry. For locally created Hub users, these properties are set manually.

For LDAP users this means that each device in the system must be able to access the user accounts. This usually means the server is joined to a domain (although in Linux, you can setup SSSD without technically joining the domain).

In Linux, you may also configure the hub to use PAM, to ensure the operating system creates the user directories and audits sessions on workers. For more information see Linux Pluggable Authentication Modules (PAM).

Ondemand API, Library server

A workload is run using an OS account. This is automatically created in Linux, but must be configured in Windows, see the sections On Demand API and Library Server for details