[KB3290] Getting started with ESET Secure Authentication (ESA)

Complete or verify each installation prerequisite before proceeding to step 2.

• An Active Directory domain or local area network
• Verify your server and clients are running the following supported software:
  • Operating systems
  • Web browsers
  • Web applications
  • Mobile phone operating systems
  • Active Directory (AD) environments if installing on an Active Directory environment
• Outbound connectivity to esa.eset.com on TCP port 443.
• If installing on an Active Directory environment for the first time, a member of the "Schema Admins" security group must complete the install. Otherwise, a user with administrator privileges is required to complete the install.
• Active Directory (AD) users using ESA to protect Microsoft Exchange for Outlook Web App (OWA) must have mailbox accounts with OWA (this application is optional for other users)

For more specific requirement information, review the Requirements section of the ESET Secure Authentication user guide.

Install the ESET Secure Authentication (ESA) Server. When the ESA Server is installed, continue to step 3 below.

To activate your ESET Secure Authentication (ESA) license:

1. Launch the ESA Web Console.
    
2. Click Dashboard.
   
   
3. Click License and enter your username and password and then click Activate. You can alternatively click ESET PROTECT Hub or ESET Business Account or ESET MSP Administrator depending on your preference.

Install and configure the ESET Secure Authentication (ESA) mobile application on all client phones. When entering mobile telephone numbers for users, use the following format: international code/area code/telephone number (for example, +16195555555, where +1 is the international code and 619 is the area code).

• Android
• iPhone
• Windows Phone

For more information on ESET Secure Authentication (ESA) topics and troubleshooting ESA-related issues, refer to the topics below:

• To authenticate using a VPN and SMS one-time password (OTP), enter the unique OTP when the system prompts a second time for credentials. During two-factor authentication using SMS messages on a VPN, an end-user might confuse the second password prompt and attempt to re-enter their Active Directory credentials. If they submit the wrong credentials too many times, that user will be locked out and will not be able to authenticate until the administrator unlocks their account. 
• ESET Secure Authentication (ESA) Online Help guide