Table of contents
Add asset configuration to jumpserver bastion host
1. Create a jumpserver management user and log in to the jumpserver bastion machine
2. Create a normal user and manage the resource server
3. Create a privileged user and log in to the resource server
6. Log in to jumpserver and create the jumpserver user
7. Administrator monitors users
Add asset configuration to jumpserver bastion host
Create three users, jumpserver management user, privileged user, and ordinary user
1. Create a jumpserver management user and log in to the jumpserver bastion machine
User creation details
There will be an email prompt after creation.
2. Create a normal user and manage the resource server
Creation details:
The effect is as follows:
3. Create a privileged user and log in to the resource server
Create details
The effect is as follows:
4. Add resources
Create details
The effect is as follows:
Wait for a while, refresh the view, and the configuration information will appear.
Enter to view
ps note:
Connectable status prompt circle,. what to do?
Go to this page
Click on the right to test
The effect is as follows:
The status changes to “Green√”
5. Asset authorization
Create details
The effect is as follows:
6. Log in to jumpserver and create the jumpserver user
reset Password:
I received a password change prompt in my email:
Log in again
Click on the workbench
my assets
Can log in
Login options appear
At this time, it is displayed as user01, but we can check the resource server.
There is no such account
Then let’s log in and test it! Shows successful connection!
Let's check the /etc/passwd file of the resource server again. User user01 appears, but you don't know the password because you are an ordinary user and you set a managed password, relying on the password created by the jumpserver bastion machine!
7. Administrator monitors users
In the administrator interface, audit desk
Session records are displayed as follows:
Click to monitor! Can monitor current operations in real time
Of course, it can also be disconnected, just disconnect the operation!
The effect is as follows:
The client directly disconnects
You can check the command log to see what was done.
Historical sessions, view work videos
Logs can also be viewed
