No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CloudEC V600R019C00 Security Maintenance (Enterprise On-premises, Only Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Managing Accounts

Managing Accounts

After the SMC2.0 is installed, three types of users are provided by default. Each type of users can only add, modify, and delete users with lower levels.

  • Administrator: have all rights.
NOTE:

The Administrator user can add, delete, and modify all the other system administrator accounts.

  • Conference administrator: have conference management rights.
  • Operator: have permission to operate active conferences.

These default user types, as well as the rights assigned to them, cannot be deleted or changed.

You can add new user types and assign rights to them.

Adding a User Type

You can add new user types and assign rights to them.

The operation procedure is as follows:

  1. Choose Settings > User Type to display the User type page.
  2. In the left pane, click

    to display the Define New User Type window, as shown in Figure 2-1.
    Figure 2-1 Define New User Type

  3. In Type name, enter the name for the new user type.
  4. Assign rights to the new user type, and click Save to save the settings.

Adding a Local User

Operation Procedure
  1. Choose Settings > User to display the User page.
  2. Select an organization to which you want to add a user.
  3. Click Add User to add a user.

    Figure 2-2 Adding a Local User

  4. Enter the user information, among which, Email is for entering the email address for receiving conference notifications and password information.
  5. Click OK.

    A dialog box is displayed, indicating a user has been successfully added.

  6. Click OK.
Verifying the Result

After a new user logs in to the SMC2.0 using the initial password, the user will be prompted to change the password.

Resetting a Password

If a user forgets the user password, the user can ask the system administrator to reset it.

The operation procedure is as follows:

  1. Choose Settings > User to display the User page.
  2. Choose a user for whom you want to reset the password and click Reset Password.

    A Reset user password dialog box is displayed.

  3. Enter the password information and click OK.

    A dialog box is displayed, indicating the password has been successfully reset.

  4. Click OK.
    NOTE:

    The user whose password has been reset receives an email containing the new password. When logging in to the web interface next time, the user will be prompted to change the password.

Changing the Password

To improve system security, change the password periodically.

NOTE:

When you change the password, the connection to the web interface automatically changes to an HTTPS connection for enhanced data security.

The operation procedure is as follows:

  1. Click in the upper right corner of the page to display the Change User Password dialog box, as shown in Figure 2-3.

    Figure 2-3 Change User Password

  2. In Current password, enter the current password. In New password and Confirm new password, enter a new password.
  3. Click Save.

SMC2.0 Password Complexity Requirements

Table 2-1 lists the complexity requirements for passwords used on the SMC2.0.

Table 2-1 Password complexity requirements

Type

Scenario

Complexity Requirements

User

User adding

The system generates a random password.

At the first login to the SMC2.0, you are required to change the password.

Password resetting

Password changing

  • Must contain a minimum of eight characters.
  • Cannot be the same as the reverse of the user name.
  • Must contain characters from at least two character classes: uppercase letters, lowercase letters, digits, and common special characters.

Conference, chair, activation

Conference template defining

A random string with six digits is automatically generated.

Conference scheduling

Database key backup

Decompression password

  • Must contain a minimum of eight characters.
  • Must contain characters from at least two character classes: uppercase letters, lowercase letters, digits, and common special characters.

Domain user

SMC2.0 login.

When changing the password, adhere to the following rules:

  • Must contain a minimum of eight characters.
  • Must contain characters from at least two character classes: uppercase letters, lowercase letters, digits, and common special characters.

FTP account for obtaining a network address book

NOTE:

Common special characters include: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ?

Common special characters do not contain commas (,) or spaces.

SC Password Complexity Requirements

Table 2-2 lists the complexity requirements for passwords used on the SC.

Table 2-2 Password complexity requirements

Type

Scenario

Complexity Requirements

SC

Authentication password for registering with the GK

When changing the password, adhere to the following rules:

  • Must contain a minimum of eight characters.
  • Must contain characters from at least two character classes: uppercase letters, lowercase letters, digits, and common special characters.

Authentication password for registering with the SIP Server.

Authentication password for SC routingd

NOTE:

Common special characters include: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ?

Common special characters do not contain commas (,) or spaces.

Unlocking a User

If a user enters incorrect passwords ten times when logging in to the SMC2.0, the user account will be locked for 30 minutes (a default value). The administrator can unlock locked standard users. If the administrator is locked out, it can only be unlocked by the SMC2.0 automatically after the lock time.

NOTE:

On the SMC2.0 web interface, you can choose Settings > Settings > Security Policy to set In time period (min.), If login attempts reach, and Account will be locked (min.).

The operation procedure is as follows:

  1. Choose Settings > User to display the User page.
  2. Select a user you want to unlock.
  3. Click Unlocked.

Locking the IP Address

To prevent malicious login, the SMC2.0 locks the IP address of a user's PC when the user fails to log in to the SMC2.0 web interface using two different accounts consecutively because the numbers of password entry attempts for both the two accounts exceed the threshold. During the lockout duration (2 hours by default), the user cannot log in to the SMC2.0 using any account. When the lockout duration elapses, the SMC2.0 automatically unlocks the IP address.

To set whether to enable the function of locking the IP address, number of failed login accounts for triggering IP address locking, and lockout duration, refer to the SMC2.0 Uncommon Function Configuration Guide.

Session Management

After logging in to the SMC2.0 web interface, the admin user can view session information about all online users and delete sessions from the session list.

Operation Procedure
  1. Choose System > Session List. The Session List page is displayed.

    NOTE:

    In the session list, you can view online users' session information, including the user IP address, user name, source type, source, login type, login language, and login time.

  2. Select a session from the session list and click End Session in the upper right corner of the page. The session is ended, and the corresponding user is logged out of the system.
Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059091

Views: 16689

Downloads: 9

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next