2
0
mirror of https://github.com/pikvm/pikvm synced 2024-11-16 12:12:57 +00:00
pikvm/docs/auth.md

133 lines
4.8 KiB
Markdown
Raw Normal View History

2023-01-23 12:44:49 +00:00
# Authentication
2023-08-20 07:04:39 +00:00
!!! warning "PiKVM comes with the following default passwords"
2023-01-23 12:44:49 +00:00
2023-08-20 06:59:53 +00:00
* **Linux admin** (SSH, console, etc.): user `root`, password `root`.
* **PiKVM Web Interface** ([API](api.md), [VNC](vnc.md)...): user `admin`, password `admin`, no 2FA code.
2023-01-23 12:44:49 +00:00
2023-08-20 06:59:53 +00:00
**These are two separate entities with independent accounts.**
!!! note "There is another special Linux user: `kvmd-webterm`"
It can't be used for login or remote access to PiKVM OS and has the non-privileged rights in the OS.
Password access and `sudo` is disabled for it. It is used only for launching the Web Terminal.
These restrictions are set for security reasons.
*Changing the [VNCAuth passkey](vnc.md) and [IPMI password](ipmi.md) described in the relevant documents*.
2023-08-20 04:04:07 +00:00
-----
## Root access in the Web Terminal
2023-08-20 04:35:54 +00:00
As mentioned above, the Web Terminal runs under user `kvmd-webterm` with disabled `sudo` and password access.
2023-08-20 04:04:07 +00:00
However, most PiKVM administration commands require the `root` access.
2023-08-20 04:35:54 +00:00
To obtain it in the Web Terminal, type `su -` and then enter the `root` user password:
2023-08-20 04:04:07 +00:00
2023-08-20 04:35:54 +00:00
```console
2023-08-20 04:04:07 +00:00
[kvmd-webterm@pikvm ~]$ su -
...
[root@pikvm kvmd-webterm]#
```
2023-08-20 06:59:53 +00:00
??? example "Step by step: Disabling the Web Terminal"
2023-08-20 04:16:51 +00:00
Sometimes the actual owner of a PiKVM device and the user who is allowed to use it are different people.
So you may want to disable console access from the Web UI. To do this, use the following:
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:16:51 +00:00
[root@pikvm ~]# rw
[root@pikvm ~]# systemctl disable --now kvmd-webterm
[root@pikvm ~]# ro
```
For your own access to PiKVM OS, you will still have SSH.
2023-08-20 04:04:07 +00:00
-----
2023-03-23 23:08:56 +00:00
## Changing the Linux password
2023-01-23 12:44:49 +00:00
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:04:07 +00:00
[root@pikvm ~]# rw
[root@pikvm ~]# passwd root
[root@pikvm ~]# ro
2023-01-23 12:44:49 +00:00
```
2023-08-20 04:04:07 +00:00
-----
2023-03-23 23:08:56 +00:00
## Changing the KVM password
2023-01-23 12:44:49 +00:00
2023-08-20 06:59:53 +00:00
This password is used, among the Web UI login, to access the [API](api.md), [VNC](vnc.md) (if enabled)
and other functions that do not concern the OS shell.
2023-08-20 08:44:47 +00:00
By default, an authentication method similar to Apache Server is configured: users and passwords
are stored encrypted in the `/etc/kvmd/htpasswd` file. To manage them, there is a utility `kvmd-htpasswd`.
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:04:07 +00:00
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-htpasswd set admin
[root@pikvm ~]# ro
2023-01-23 12:44:49 +00:00
```
2023-08-20 04:04:07 +00:00
Please note that `admin` is a name of a default user. It is possible to create several different users
2023-01-23 12:44:49 +00:00
with different passwords to access the Web UI, but keep in mind that they all have the same rights:
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:25:31 +00:00
[root@pikvm ~]# kvmd-htpasswd set <user> # Sets a new user with password
[root@pikvm ~]# kvmd-htpasswd list # Show the list of users
[root@pikvm ~]# kvmd-htpasswd del <user> # Removes/deletes a user
2023-01-23 12:44:49 +00:00
```
2023-08-20 08:44:47 +00:00
At the moment there is no way to create any ACL for different KVM users.
2023-08-20 06:59:53 +00:00
2023-08-20 04:04:07 +00:00
-----
2023-01-23 12:44:49 +00:00
## Two-factor authentication
This is a new method of strengthening the protection of PiKVM, available since `KVM >= 3.196`.
It is strongly recommended to enable it if you expose the PiKVM in the big and scary Internet.
!!! warning
2023-08-20 04:04:07 +00:00
Using 2FA eliminates the possibility of using [IPMI](ipmi) and [VNC with vncauth](vnc) (both disabled by default).
It also slightly affects the use of [API](api.md) and regular VNC with user/password, read below.
Please note that 2FA does not concern the Linux OS access for the `root` user, so take care of a strong password
for it for SSH access (or setup the [key access](https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server)).
??? example "Step by step: Enabling 2FA on PiKVM"
2023-01-23 12:44:49 +00:00
2023-08-20 04:04:07 +00:00
1. Update OS and reboot:
2023-01-23 12:44:49 +00:00
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:04:07 +00:00
[root@pikvm ~]# rw
[root@pikvm ~]# pacman -Syu
[root@pikvm ~]# reboot
```
2023-01-23 12:44:49 +00:00
2023-08-20 04:04:07 +00:00
2. **Make sure that NTP is running otherwise you will not be able to access** (`timedatectl` command).
The timezone doesn't matter.
2023-01-23 12:44:49 +00:00
2023-08-20 04:43:09 +00:00
3. Install the **Google Authenticator** app to your mobile device
2023-08-20 04:04:07 +00:00
([iOS](https://apps.apple.com/us/app/google-authenticator/id388497605),
[Android](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2)). It will generate one-time access codes.
2023-01-23 12:44:49 +00:00
2023-08-20 04:04:07 +00:00
4. Create a secret for one-time codes on PiKVM:
2023-08-20 04:43:09 +00:00
```console
2023-08-20 04:04:07 +00:00
[root@pikvm ~]# rw
[root@pikvm ~]# kvmd-totp init
[root@pikvm ~]# ro
```
2023-01-23 12:44:49 +00:00
2023-08-20 04:43:09 +00:00
5. Run the Google Authenticator and scan the QR code.
2023-01-23 12:44:49 +00:00
2023-08-20 04:04:07 +00:00
6. Now, on the PiKVM login page, you will need to add 6 digits to the `2FA code` field.
2023-01-23 12:44:49 +00:00
2023-08-20 04:04:07 +00:00
All Web UI users will be required to enter a one-time password on login.
In other words, **the secret is the same for all users**.
2023-01-24 04:37:48 +00:00
2023-01-23 12:44:49 +00:00
!!! note
2023-08-20 04:04:07 +00:00
With 2FA for API or VNC authentication, you will need to append the one-time code to the password without spaces.
2023-01-24 04:37:48 +00:00
That is, if the password is `foobar` and the code is `123456`, then you need to use `foobar123456` as the password.
2023-01-23 12:52:27 +00:00
2023-08-20 04:04:07 +00:00
To view the current QR code of the secret use command `kvmd-totp show`.
2023-01-23 12:52:27 +00:00
2023-08-20 04:04:07 +00:00
To disable 2FA and remove the secret, use command `kvmd-totp del`.