This is the sixth day of my participation in the August More text Challenge. For details, see:August is more challenging

1. The previous chapter introduced user management. There are also users to manage in asset management, so we need to distinguish the difference between management users and system users.

2. Before adding an asset, create the user corresponding to the asset first: Note that there is a menu explaining the functions of the data in the list in the menu expanded on the left;

3. Create system user: Note the points marked in the figure:

  • The first login mode is associated with the fourth automatic push. If it is manual login, there is no need for management users to push system user login to the server. And if it is associated with the sixth login, there is no need for automatic password generation
  • The second point means that the system user is created with the same name as the user managed by the user, so the user logging in to the Web is pushed to the past as the system user of the asset server and the password needs to be set: < at this time, check the automatic password generation to log in the asset is invalid >;
  • The third point is to select the protocol. If there are assets of other protocols such as mysql, you need to create system users of different protocols, which will be mentioned again in the application management
  • The fourth point means that the administrative user pushes the system user to the asset server < that is, create user >
  • If you need to switch the management user to su – root, a message will be displayed indicating that the system user authentication fails. In this case, you can add /usr/bin/su and enter su root to avoid changing the management user
  • The sixth is used in conjunction with the fourth to automatically push the user to the asset and generate the password automatically
  • The seventh point is used in conjunction with the first
  • Eighth, you need to create an SSH login password on the asset server.
  • Ninth, you need to filter the commands in asset management. Create Linux commands that need to be filtered out and do not allow specific system users to use them
  • The tenth point is the temporary directory of the SFTP server where the asset server is located: / TMP. All files to be downloaded from the asset server must be transferred to/TMP first. Then right-click Server Download from session Management – File Management

4, after the creation of management users and system users, you can enjoy the unified management of all assets to be managed:

Tips: An authenticated admin user is a user with super permission < create admin user first >; The asset list tree menu allows you to right-click to create a node that can be used to mount the asset directory for the bed frame.