Skip to main content
The role combines repetitive authority, the grant gives you a specific permission. Separate panel capabilities, node area, system login and allowable operations, so you can delegate access control without issuing a terminal, or allow you to work with one group of servers without managing the entire installation.

What rights should be distinguished

The owner has special powers. A named role with inheritance does not become an owner simply because of the name or connection with another role.

Creating a role

In Access Roles run the wizard. Set a clear name and description of the task, for example, Operators of the test environment. Select interface rights, then access to nodes and, if necessary, parent roles. Before saving, check the result. The rights matrix divides viewing and managing users, nodes, agents, bastions, projects, imports, roles, grants, sessions, records, security, and automation. Select human authority: the service operator does not have to manage other users or security policies. Once you’ve created, assign participants. Assigning a role to the user and giving a node access role — both steps are needed to make the resolution work.

Selection of nodes and system login

For the role, you can choose specific nodes, groups, tags, or all nodes. Groups and tags are a dynamic choice: the future suitable machine will fall under the rule. If access is to be left only on current servers, choose them explicitly. User Personal Accounting is suitable for individual system login. Telepúrte will prepare it through the agent, and the role will determine where the login is allowed. Existing system login is needed if the work is to go under the already created meter. Separately check the need for groups, sudo shell and commands. Some permissions have a deadline; SSH can also be indefinite. Check the date and time zone in the final summary.

Inheritance and prohibitions

A role can inherit other roles. Permissions add up, but the current prohibition takes precedence over permission. Prohibition can refer to a user or role, an individual node, a project, a group, a tag, or an entire area; for files, path is additionally taken into account. Don’t expect to add a wider role to override a narrow ban. In file rules, look carefully at unselected actions: a restriction from one role may prohibit an action that is allowed by another. A direct, valid SSH grant takes precedence over a role grant, and once it expires, it can become valid access from the role again, so the completion of a temporary direct grant does not always mean a complete lack of access.

One-time grant to the user

In SSH Grants, select a recipient, nodes, groups or tags. Determine whether an existing login is used or a prepared managed ledger, select groups and a deadline, check the list of servers and save. When preparing the meter, wait for the readiness of each node. A Linux group error, an outdated agent or a ban on managed accounts should not be avoided by issuing root without indiscriminate cause. A delegated access manager works only in its own project area and does not automatically receive SSH, assignment rights, or other people’s session records.

An example of a role for a test environment

Create a env=test group. Give the node viewing roles and access to the node group through a personal account. Do not turn on sudo if the task is limited to the application files in the user’s directory. Assign a role to the test operator and wait for the meter to be prepared. Check the env=test login and the env=prod opt-out. Then add a new test node: it should fall into the rule area after preparation. If not required, replace the group with a clear list.
Web SFTP file bans are not an isolation of the interactive shell. A user with a terminal and sufficient Linux rights can work with files with commands. Limit system logging and sudo according to the task.

Verification

Check the result against the recipient: partition visibility, access to the desired node, actual system login and out-of-area denial. If you have unexpected access, check direct grants, all roles, inheritance and access from Axottle.

Rollback

Withdraw an erroneous grant, withdraw a role assignment, or archive it. Rights are double-checked when appeals are made, existing connections are closed when permission is lost, an action already issued to an agent can be terminated; revocation of a role does not cancel the change made. Managed Linux accounts require a compatible agent and a permitting local policy.