|
20 | 20 | !!! tip "" |
21 | 21 | - JumpServer supports bulk associating one account with multiple assets (account adding feature). Click the **Add** button on the account list page, select the assets to associate with the account, fill in the account details, and bulk associate the account with the assets. |
22 | 22 |  |
| 23 | + |
| 24 | +| Parameter | Description | |
| 25 | +| ------------------- | ------------------------------------------------------------ | |
| 26 | +| Name | User identification name, can be repeated. | |
| 27 | +| Username | Login account for accessing JumpServer, cannot be repeated. | |
| 28 | +| Privileged Account | Accounts to be executed first during batch processing; supports duplicate settings. | |
| 29 | +| Su Switch | This account switched to another account | |
| 30 | +| Asset | Select created assets from the list; multiple selections are allowed. | |
| 31 | +| Password | Authenticate with a password encrypted by the algorithm, suitable for logging in to assets via protocols such as SSH and RDP. | |
| 32 | +| SSH Key | Implement passwordless login by configuring the private key file; the corresponding public key needs to be configured on the asset, supporting OpenSSH format. | |
| 33 | +| Token | Typically used for the ciphertext type required when creating Kubernetes asset accounts | |
| 34 | +| Password Changeable | When enabled, JumpServer can periodically change the password of this account on the asset through the account password change function. | |
| 35 | +| Account Policy | When creating an account, if the key type is non-compliant, it restricts the key (Skip / Update / Fail). | |
| 36 | +| Skip | When the account policy is executed, if the account does not meet the conditions or does not require processing, the system will skip this account without any operation. | |
| 37 | +| Update | Indicates that the system will update the permissions or configuration of the account according to the policy, such as modifying the permission scope or validity period. | |
| 38 | +| Fail | Indicates that an error occurred during the application of the account policy, such as insufficient permissions, unreachable target asset, or configuration conflict, resulting in the policy not taking effect. | |
| 39 | +| Active | Restrict normal account login | |
| 40 | +| Remarks | Optional field, used to fill in the account description information, which is convenient for administrators to identify and manage. | |
| 41 | + |
23 | 42 | ### 2.4 Add account template |
24 | 43 | !!! tip "" |
25 | 44 | - Click the **Template Add** button on the account list page, select the assets to associate the account template with, choose the account template to add, and bulk associate the account template with the assets. |
26 | 45 |  |
27 | 46 |
|
| 47 | +| Parameter | Description | |
| 48 | +| ------------------- | ------------------------------------------------------------ | |
| 49 | +| Template | Select an existing account template. | |
| 50 | +| Node | Set an existing node; you can select the authorized node corresponding to the asset. | |
| 51 | +| Asset | Select a created asset from the list. | |
| 52 | +| Password Changeable | When enabled, JumpServer can periodically change the password of this account on the asset through the account password change function. | |
| 53 | +| Account Policy | When creating an account, if the key type is non-compliant, it restricts the only action (Skip / Update / Fail). | |
| 54 | +| Active | Restrict normal account login | |
| 55 | +| Remarks | Optional field, used by administrators to configure remark information for this account template. | |
| 56 | + |
28 | 57 | ## 3 Virtual accounts |
29 | 58 | !!! tip "" |
30 | 59 | - In certain scenarios during authorization rule creation, virtual accounts are used to log in to assets. The virtual account page supports viewing details of virtual accounts. JumpServer supports allowing AD/LDAP users to log in to assets with JumpServer user passwords when authorization rules authorize accounts with the same name. |
|
0 commit comments