Skip to main content
The Telepúrte account identifies who is logged in. The servers are accessed separately, by roles, grants and a system user on the node. One person can work through their personal Linux account on different servers, keeping a single profile and history in Telepúrte.

Where do users come from?

Login matching does not combine local and imported profiles. When issuing rights, check the source of the user.

Create a local user

In Users open the creation of the account, set the username and password according to the current policy, select the necessary roles. If necessary, add a public Ed25519 SSH key. The user’s private key remains on his device. The first time you log in, the user completes the MFA setup. Before that, the password itself does not open a full session. Roles determine the panel’s capabilities and access; the new meter does not automatically receive the entire park. The other option is an invitation. The administrator creates it for the login and transmits the one-time code in a trusted way. The user accepts the code on the Telepúrte site, sets the password and sets up the MFA. The code is valid for 24 hours; re-issuing the login cancels the previous one. The code is displayed once, the invitation itself does not issue an SSH.

MFA and backup codes

Local users connect the TOTP application. Backup codes are shown once - save them separately from the working browser. Using the backup code triggers the recovery of the second factor: the previous sessions, TOTP and the remaining old backup codes are recalled, then you need to connect the application again. In the personal account, the user manages the password, the second factor, backup codes and their own connections. Sensitive changes require valid password and factor confirmation. If access is lost by the local owner, is used to restore on the server, rather than creating a new owner on top of the data.

User page

Click the name in the list. The profile is divided into tabs:
  • Review – Identity, Source of Entry, Term, Roles, Direct Grants and Recent Events
  • Roles and access Role assignments, SSH grants, Linux profile and public keys.
  • Sessions - panel authorization, SSH/SFTP and available records.
  • Audit - events where the user performed an action or was its recipient.
  • Administration - Accounting period, local password reset and disconnection.
Resetting the password of another local user closes the login and SSH sessions, but saves the MFA and grants, and this operation does not apply to the administrator’s own login, the owner, the disabled profile or the SSO user.

Personal Linux login

For a regular user, Telepúrte supports a stable personal system login. Select Personal user account. The agents supporting this function create and maintain accounting on verified managed nodes; the right of entry is still determined by the role or grant. The profile shows the system login, the groups and the number of nodes in the “ready”, “waiting”, “error” states. On the offline node, the preparation is waiting for the agent. The entry opens after the node is confirmed. If the agent is outdated or local policy does not allow managed records, the profile will show the cause. The personal login does not have a reusable Linux password. The user can connect to it through the permitted Telepúrte paths; creating a login does not allow login to all machines.

Groups and sudo

Groups from a user’s profile operate on their nodes, groups of roles act on their nodes within that role. Current sources are combined, including inherited roles. If sudo is allowed by at least one source, the absence of that permission in the other role does not cancel it. The explicit sudo resolution creates a separate, proven rule, NOPASSWD. Once the last source is removed, the appropriate managed settings are removed. Other people’s accounts and sudoers files are not assigned. The node must allow managed ledgers and the desired existing Linux groups.

Disabling the user

Disabling closes authorization and revokes access. For an imported profile, this is a local solution: the Axottle user is not deleted. The locally disabled profile is not turned back on by another synchronization. Disabling the merchandise in the current API has no back-up effect of enabling - use a review of a specific role or grant if you need a temporary suspension of separate access.

Verification

Log in under the new user, check the MFA, visible partitions and nodes. On the allowed machine, run whoami and id: login and groups must match the purpose. Check that there is no access to the machine outside the role area.

Rollback

Remove an erroneous role or grant, revoke an unnecessary public key, and wait for your personal Linux profile to be synchronized. To cancel a sudo, delete all the sources of its issuance. Disabling a profile does not return changes that a person has made on the servers. Managed Linux accounts require a compatible agent and a permitting local policy.