-
-
Notifications
You must be signed in to change notification settings - Fork 129
User authentication and roles
Eugene edited this page Sep 13, 2022
·
5 revisions
In the previous example, we've reused the Warpgate's admin
user, which only had a password as its only way to authenticate. Currently, Warpgate supports passwords, public keys or password+public key as authentication methods.
Log into the Warpgate admin UI and navigate to Config
> Users
> admin
and click Change
next to the password credential:
![image](https://user-images.githubusercontent.com/161476/189997150-7cfb9721-69e0-4083-b2a8-5c06d92f2282.png)
- Grab the user's public key in OpenSSH format (normally, you can just copy the
~/.ssh/id_<type>.pub
file contents and strip the name, leaving just<key type> <public key bytes>
, e.g.:
ssh-ed25519 AAAAC...bD4I
- Click
Add public key
and paste it:
![image](https://user-images.githubusercontent.com/161476/189997284-273478eb-634e-4cc9-8ad8-5d9d2a5f8df4.png)
Warpgate can require a client to present both a public key and a password.
- In the
Auth policy
>SSH
section, uncheckAny credential
and select bothPassword
andKey
:
![image](https://user-images.githubusercontent.com/161476/189997437-8cba652c-7ff4-43f4-83fc-9ec6492ab351.png)
You can use roles to grant a new user access to multiple targets at once (or assign multiple users to a target).
- Create and remove roles under
Config
>Roles
. - Assign roles to users and targets on their respective configuration pages.