Quickstart
This end-to-end guide takes you from installation to your first authorized asset session. It combines first login, Console orientation, asset setup, authorization, connection, and audit into one flow.
You can watch the video below or follow the steps in order.
Before you begin
You need:
- A running JumpServer installation. See Installation.
- The URL of the deployment and the initial administrator account.
- A test asset (for example, a Linux host) that JumpServer can reach.
Sign in and secure the account
- Open
https://<jumpserver-host>/in a current browser. - Sign in with the initial account: username
admin, passwordChangeMe. - Complete the forced password change and sign in again.
The default password is public. Change it immediately and do not reuse it for other systems. If MFA is required by the platform policy, complete MFA setup before continuing.
Get oriented in Console
After login, the area switcher at the top-left moves between Console, PAM, Audits, and Workbench. System administrators can open System Settings from the gear icon.
Console is the administration workspace. Its left menu is organized as follows:
The recommended setup order is: users and groups → assets → accounts → authorizations → ACLs → verify access from Workbench. The steps below follow that order for a single test asset.
Create an asset
At the top-left of the page, select , then click Console.
Navigate to the Console > Assets > Host tab.
Click Create to open the platform selection page on the right.
Select the Linux platform and open the asset creation page.
In the Name field, type a name for the asset, such as "Demo Linux".
In the IP/Host field, type the IP address of the asset, such as "172.16.10.110".
In the Linux field, keep the "Linux" platform selected.
In the Nodes field, select the "/DEFAULT" node.
In the Accounts field, click the Add and follow the steps in the pop-up to complete the account creation.
In the Name field, type a name for the account, such as "root".
In the Username field, type the username for the account, such as "root".
In the Secret type field, select "Password".
In the Password field, type the password for the account.
For other fields, keep the default values.
click Confirm.
For other fields, keep the default values.
Click Submit.
Authorize the asset
At the top-left of the page, select , then click Console.
Navigate to the Console > Authorization page.
Click Create to open the authorization creation form on the right-side page.
In the Name field, type a name for the authorization, such as "Authorize Demo Linux to Administrator".
In the Users field, select the "Administrator(admin)".
In the Assets field, select the "Demo Linux".
In the Accounts field, check only the box for "All existing accounts".
For other fields, keep the default values.
Click Submit.
Connect to the asset via the web
In the right area of the top navigation bar, click .
At this point, the Web Terminal page should be open in a new browser tab.
In the authorization tree on the left side, search for and click the "Demo Linux" asset.
An asset connection pop-up will appear, select connection parameters and establish the connection.
Select the "SSH" tab, under the "Connect - Demo Linux".
In the Select account section, Select "root".
In the Connect method section, Select "Web > Web CLI".
Click CONNECT.
By this time, you should have successfully connected to the asset.
Next, you can try executing commands such as ls -al, whoami or pwd, etc.
Finally, run exit to end the current session.
Audit the session
At the top-left of the page, select , then click Audits.
Navigate to the Audits > Asset sessions > Historical sessions tab.
You can view the history of asset connection sessions.
In the Actions column, click "Playback" to watch the recording online or "Download" to save it.
Audit executed commands
At the top-left of the page, select , then click Audits.
Navigate to the Audits > Session commands page.
You can view all executed commands.
Click at the end of the row to view the command result.
Next steps
Now that you have completed the quickstart flow, continue with the module that matches your work: