This topic answers common questions about installing and logging on to the Secure Access Service Edge (SASE) client.
Which operating systems does the SASE client support?
Windows, macOS, and Linux. For more information, see Install and log on to the SASE client.
Why does the SASE client take a long time to install?
If .NET Framework is not installed on your terminal, the installer downloads and installs it before proceeding with the SASE client. This is expected behavior — wait for the process to complete.
What do I do if I cannot log on to the SASE client?
The most common causes are:
Network connectivity: Run the following command to test whether the SASE service is reachable. If the host is unreachable, work with your network team to verify that outbound traffic to
saml-csas.aliyuncs.comis allowed.ping saml-csas.aliyuncs.comDNS resolution failure: If the ping command returns an error about the host not being found (rather than a timeout), the issue is likely DNS resolution. Work with your network team to confirm that
saml-csas.aliyuncs.comresolves correctly.
The SASE client shows a white screen and a "bad request" error after I enter my enterprise authentication identifier. What do I do?
Cause: Your enterprise administrator has not added you to the custom identity provider (IdP).
Resolution: Contact your administrator and ask them to add your account. After that, try logging on again. For configuration details, see Configure a SASE IdP.
Can users uninstall the SASE client?
If the administrator of the enterprise has configured terminal anti-uninstallation policies, a user must submit an uninstallation application through the SASE client. The user cannot uninstall the SASE client until the administrator approves the request.
For more information, see Configure an anti-uninstallation policy and approve an uninstallation application.