Entrance through Axottle
The user chooses to log in via Axottle, confirms the transition and, if necessary, passes the MFA according to Telepúrte’s policy. The external account is linked using the stable Axottle identifier. The matching local username does not combine the two accounts. Synchronization creates profiles in advance, but does not create a login session or assign a local owner role.Addition of nodes
1
Check the imports
Open Import Axottle to Telepúrte. Make sure the right nodes, their IP and designs are in the directory. Axottle sends inventory after launch and then once per minute.
2
Launch the connection.
For one node, press Add in its line, for the park - Add all. Confirm the Axottle Agent update and start the task.
3
Wait for the prep.
The task updates the agent, connects it to Telepúrte with a separate identification, prepares the SSH and checks the host key. It continues to run after the page is closed. The results of successful and unsuccessful connections are shown separately.
4
Check the terminal.
After successful preparation, check the owner’s SSH access. A configured Telepúrte gateway with an HTTPS route should be available for the browser terminal and Web SFTP.
Rights of users and projects
Project membership is transferred from Axottle, which limits access, but does not allow SSH by itself. Use Telepúrte’s individual permissions and roles to access. Axottle also has an explicit user setting Access to all SSH machines of designated projects. When enabled, Telepúrte creates controlled access underroot to the machines of these projects. Disabling revokes this access; separately issued Telepúrte roles and permissions continue to operate within the membership.
File transfers and agent operations have their own limitations, and being able to open a terminal does not mean permission to any file path or bulk task.
Synchronization and recall
The user list is updated once a minute, and if the fresh list is not received for three minutes, the access of the imported accounts is suspended, including open connections, and the owner’s local login remains a separate recovery method. An inactive or disappeared account is blocked from the recipient. The return of the active state does not include the profile that the local owner disabled in Telepúrte. The disappearance of the node from Axottle also does not delete its history in Telepúrte.Typical problems
For conflicts of the former SSH CA, the Telepúrte Agents section provides a massive replacement with explicit confirmation. Requires Axottle Agent 1.3.15 or later. Apply it only to nodes that really need to be replaced with the previous binding.
