Added 2FA for agent screen logins
Added several campaign fields to update_settings related to manual dial calls in the agent screen git-svn-id: svn://192.168.202.10@3770 3d104415-ff17-0410-8863-d5cf3c621b8a
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# version: 20231011152901
|
||||
# version: 20231109083801
|
||||
users-user User ID <QXZ>This field is where you put the users ID number, can be up to 20 digits in length, Must be at least 2 characters in length. We strongly recommend not reusing user accounts for different users, for reporting accuracy. To disable a user account, set the Active option to -N-.</QXZ>
|
||||
users-pass Password <QXZ>This field is where you put the users password. Must be at least 2 characters in length, unless the User Password Minimum Length system setting is enabled, which will require a longer password. Only letters and numbers are allowed in user passwords. A medium strength user password will be at least 10 characters in length, and a strong user password will be at least 20 characters in length and have letters as well as at least one number. It is recommended that you use a longer password if possible, stringing together several unrelated words with no spaces, and a number somewhere in the string. The maximum size of a password is 100 characters.</QXZ>
|
||||
users-force_change_password Force Change Password <QXZ>If this option is set to Y then the user will be prompted to change their password the next time they log in to the administration webpage or the agent screen. Default is N.</QXZ>
|
||||
@@ -1216,7 +1216,8 @@ settings-mute_recordings Allow Mute Recordings <QXZ>This option if enabled allow
|
||||
settings-enable_auto_reports Enable Automated Reports <QXZ>This option if enabled allows you access to the Automated Reports section where you can set up reports to run at scheduled times and be delivered by email or FTP. Default is 0 for disabled.</QXZ>
|
||||
settings-first_login_trigger First Login Trigger <QXZ>This setting allows for the initial configuration of the server screen to be shown to the administrator when they first log into the system.</QXZ>
|
||||
settings-require_password_length User Password Minimum Length <QXZ>If set above 0, this setting will require that user passwords, phone and server passwords, and system settings default passwords be at least this minimum length of characters when those records settings are modified on the Modify pages. The most important factor in password security is the length of the password, and user passwords in this system can be up to 100 characters in length. Default is 0 for disabled.</QXZ>
|
||||
settings-two_factor_auth_hours Two-Factor Auth Hours <QXZ>Two-Factor-Authentication, 2FA for short, adds a required second step to the login process through a method other than a password, such as an Email, Phone Call or Text-Message -SMS-. This 2FA Auth Hours field is where you define the number of hours each auth will last, or until the user logs out. Currently, 2FA is not available for agent screen logins. Default is 0 for 2FA disabled. WARNING, if you enable this without properly configuring the 2FA settings container below, you will lock all users out of the admin web screens and a System Administrator will have to fix your system.</QXZ>
|
||||
settings-two_factor_auth_hours Two-Factor Admin Auth Hours <QXZ>Two-Factor-Authentication, 2FA for short, adds a required second step to the login process through a method other than a password, such as an Email, Phone Call or Text-Message -SMS-. This 2FA Admin Auth Hours field is where you define the number of hours each auth will last for a web admin user, or until the user logs out. 2FA can also be enabled for agent screen logins using the setting below. Default is 0 for 2FA disabled. WARNING, if you enable this without properly configuring the 2FA settings container below, you will lock all users out of the admin web screens, and a System Administrator will have to fix your system. Also, you will need to configure each user email and-or mobile phone number for all active web admin users.</QXZ>
|
||||
settings-two_factor_auth_agent_hours Two-Factor Agent Auth Hours <QXZ>Two-Factor-Authentication, 2FA for short, adds a required second step to the login process through a method other than a password, such as an Email, Phone Call or Text-Message -SMS-. This 2FA Agent Auth Hours field is where you define the number of hours each auth will last for agent screen users. 2FA can also be enabled for admin logins using the setting above this one. Default is 0 for 2FA disabled. WARNING, if you enable this without properly configuring the 2FA settings container below, you will lock all users out of the agent web screens, and a System Administrator will have to fix your system. Also, you will need to configure each user email and-or mobile phone number for all active agent screen users.</QXZ>
|
||||
settings-two_factor_container Two-Factor Auth Config Container <QXZ>Must be a valid 2FA_SETTINGS Container Type for 2FA to work. For more information on the settings that can be used in that container, please see the -2FA_TWO_FACTOR_AUTHENTICATION.txt- document.</QXZ>
|
||||
settings-user_account_emails User Login Link Emails Allowed <QXZ>The feature will allow you to click on a link from the User Modify page to send an email to an agent with a shortcut URL web address that will allow them to more easily log in to the agent screen. You can select options to send these emails with or without the user password included. Default is DISABLED.</QXZ>
|
||||
settings-phone_defaults_container Default Phones Settings Container <QXZ>This feature allows you to use a settings container of the type PHONE_DEFAULTS to pre-load numerous settings into the phone creation form and create new phones with these values pre-set. Refer to the PHONE_DEFAULTS settings container for an example of a container with all available settings that can be pre-set. Default is ---DISABLED---.</QXZ>
|
||||
|
||||
Reference in New Issue
Block a user