The path for these executables changes based on your installation directory. C:\Program Files\EAAClient\wappstart.bat.Navigate to the installation directory with the following command: cd /. On the Linux computer, open a terminal application window. C:\Program Files\EAAClient\wapphide.vbs Copy the installation package that you created to the Linux computer.C:\Program Files\EAAClient\wapprestart.bat.C:\Program Files\EAAClient\uninstall.exe. ![]() C:\Program Files\EAAClient\autoupdate-windows.exe.C:\Program Files\EAAClient\wapptunneld.exe.C:\Program Files\EAAClient\resources\elevate.exe.C:\Program Files\EAAClient\EAAClient.exe.If your computer has any endpoint protection software installed, you need to allow these EAA Client executables (based on your operating system):įor a Windows 7 or Windows 10 OS, when EAA Client software is installed under C:\Program Files\EAAClient\ directory, then allow: Allow the following static URLs if you use Device Posture with EAA Client: Local IP ranges that EAA Client uses to intercept traffic for TCP applications: 127.0.0.ĮAA Client network interface works with 100.64.0.1.ĭevice Posture. Local IP ranges that EAA Client uses to intercept traffic for tunnel applications/wildcard domains: 100.64.0.0/11. Local FQDN: application internal hostname. FQDN is the application external hostname as configured in Akamai Control Center. To have proper connectivity from Enterprise Application Access Cloud to the connector, you should allow certain IPs. IP address depends on where the EAA IdP cloud zone is. You may need to configure these FQDN (fully qualified domain names) and IP addresses into your corporate proxy, secure web gateway or similar equipment.Īkamai authentication portal endpoints. The FQDNs and IP addresses used by both EAA Client and Device Posture. Certificate-based validation of origin serversįQDNs and IP addresses used by EAA Client.Certificate-based device authentication or user validation in an application. ![]()
0 Comments
Leave a Reply. |