Translations:Managing your cloud resources with OpenStack/29/en: Difference between revisions

(Importing a new version from external source)
m (FuzzyBot moved page Translations:OpenStack/29/en to Translations:Managing your cloud resources with OpenStack/29/en without leaving a redirect: Part of translatable page "OpenStack")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
There are a number of ways to allow more than one person to log in to a VM. We recommend creating new user accounts and adding public [[SSH Keys]] to these accounts. To do so manually, first create a new user account (under Ubuntu, for example) with the command {{Command|sudo adduser --disabled-password USERNAME}}
==Creating an account and keys==
Then add the person's public key to the <code>/home/$USER/.ssh/authorized_keys</code> file as described in [[SSH Keys]] and linked pages.
A new user account can be created on Ubuntu with the command {{Command|sudo adduser --disabled-password USERNAME}} To be able to connect, the new user will need to have a key pair, see [[Generating_SSH_keys_in_Windows|generating SSH keys in windows]] or [[Using_SSH_keys_in_Linux#Creating a Key Pair|creating a key pair in Linux or Mac]] depending on the operating system they will be connecting from. Then their public key must be added to <code>/home/USERNAME/.ssh/authorized_keys</code> on the VM, ensuring permissions and ownership are correct as described in steps 2 and 3 of [[Using_SSH_keys_in_Linux#Connecting using a Key Pair|connecting using a key pair]].

Latest revision as of 18:42, 8 November 2022

Creating an account and keys

A new user account can be created on Ubuntu with the command

 
[name@server ~]$ sudo adduser --disabled-password USERNAME

To be able to connect, the new user will need to have a key pair, see generating SSH keys in windows or creating a key pair in Linux or Mac depending on the operating system they will be connecting from. Then their public key must be added to /home/USERNAME/.ssh/authorized_keys on the VM, ensuring permissions and ownership are correct as described in steps 2 and 3 of connecting using a key pair.