Release notes
TrainingSupportCommunity
Back to All

Jun 21, 2021 — Desktop client 3.4.0 launch

over 3 years ago by jacabral@akamai.com

A new version of the desktop client is now available.

Updates in this release include:

  • Bring Your Own Device (BYOD) Support. ​ETP Client​ 3.4.0 can now protect a user’s personal computer or laptop. A new installation process allows users to activate ​ETP Client​ on their personal machines without using the enterprise-wide entitlement code. When using this feature, consider these points:

    • After the client is installed on the user’s machine, the user is prompted to activate the client with a one-time activation code (OTAC). If the user does not have this code, the client lets users request it. The activation code is emailed to the authorized user’s corporate email address.

    • To email activation codes, administrators need to configure authorized corporate domains in Enterprise Center. Administrators should not provide email domains that are associated with unauthorized users.

    • From Enterprise Center, administrators can send users an email invitation that contains the activation code. Administrators can also choose to generate a CSV file with activation codes and manually distribute these codes to users. After the activation codes are generated, they are valid for one week (7 days).

    • When generating an OTAC in Enterprise Center, administrators should specify the user’s email address in the User’s List. This allows administrators to easily associate events with the users who trigger them. This email address appears in the new Device Owner dimension that’s available in ​SIA​ event and activity reports.

    • End users are not prompted for an entitlement code during the installation of the client. The entitlement code is used by administrators only. After installing ​ETP Client​ with the user interface, administrators enter the entitlement code in the ​ETP Client​ interface. Installations that are performed with the command line can still use the entitlement code.

  • Support for Apple M1 chip. ​ETP Client​ now supports Mac computers with the Apple M1 chip.

  • ​ETP Client​ Access Logs. New log files provide detailed information on all ​ETP Client​ traffic. These logs are formatted to make them easier for analysis. These CSV files are available in the client Log directory:

    • etp_Proxy_Access.csv: Contains logs of web traffic forwarded from ​ETP Client​ to ​SIA​ Proxy. Log data includes the time that activity occurred, ID associated with the request, requested domain, and more.

    • etp_Client_Access.csv: Contains logs of DNS traffic forwarded from ​ETP Client​ to ​SIA​ DNS resolvers. Log data includes the time that activity occurred, ID associated with the request, whether DNS over TLS (DoT) or DNS over UDP was used, and more.

    When a log file reaches 40 MB, an index value is appended to the filename and a new log file is created with the original filename. These logs can be used by your organization to review requests and troubleshoot technical issues. Administrative privileges are required to view these logs.

    Note: These logs contain all traffic, including logs for private browsing. Make sure these logs are handled securely to maintain the user’s privacy.

    ​ETP Client​ is enabled for logging by default. However, administrators can disable logging in Enterprise Center.