Creating guest access
Open Temporary access and go through the wizard:- Select a temporal scenario.
- Find specific nodes, groups or tags. Selected sources are combined without duplicates; check the final list.
- Specify the permitted Linux groups and expiration date.
- Select whether one or more simultaneous visits are allowed.
- Check the summary and create access.
Training and extradition
First, the grant is inpending. The card shows the preparation of each node. Access becomes active after confirming all the selected servers; one preparation error should not leave the guest imperceptibly stripped down set of machines.
The link is only shown when you create it. Copy it and give it to the recipient in a trusted way. The new grant also gives you a separate SSH password and system login; the password is displayed once. Do not publish the link or password in the general journal of works.
What the guest sees
The link opens a separate guest page. After sharing a secret, it only shows the nodes of this grant and the Web SSH tabs. Guest login does not open a regular panel, user management, roles or Web SFTP. The guest selects the node and works in the terminal, the connection goes through the bastion and is recorded, and when the visit ends, the recall or the deadline expires, access to the current session is terminated on the next check.Entry to a regular SSH client
Use the guest’s system login, a separate SSH password, and the bastion’s SSH address. The grant must be active. After logging in, the menu shows only the allowed machines; exiting the node returns to the menu, closing the SSH connection completes the visit. For an old valid grant without a password, the administrator can release it in a card. Reissue cancels the previous password and the SSH sessions opened with it. Browser visits continue to work: to completely close access, withdraw the grant itself.Control of work
The grant card shows server preparation, visits, time, IP, User-Agent and browser information. Related SSH sessions are available in the general list with the transition to the grant. Use the terminal record and the audit Z to analyze the actions. In case of a preparation error, first check the agent, the existence of permitted Linux groups and the local policy of managed accounts. expiration or recall triggers the deletion of managed accounts; on an inaccessible node, the actual cleanup can wait for the agent to return, although new connections via Telepúrte are already closed.Registered user application
Separately, SSH-access is supported on the application: the administrator includes a policy for the verified node, sets a non-root system login and a maximum term. The user specifies the reason and term, the owner accepts or rejects the application. The approval creates a normal temporary SSH-grant, not a guest link. This script is available through the/api/v1/access/ssh-requests application API; do not confuse it with the guest wizard.If the node, user, or policy has changed since submission, approval may require a new application.
