Usage Note 54350: SAS® Mobile BI requires your device to trust certificates used for Secure Sockets Layer (SSL) connections
If your SAS® Visual Analytics Server is configured to use Secure Sockets Layer (SSL) connections, you might need to perform additional steps in order to define a connection with SAS Mobile BI. Otherwise, you see an error similar to the following when you try to define a new connection to SAS®:
A secure connection could not be established with this server. Verify that all required certificates have been installed.
SAS Mobile BI relies on the mobile device's operating system when it makes a connection. For this reason, you should follow these recommendations when preparing SAS Mobile BI to connect to a SAS Visual Analytics server configured to use SSL connections:
- Self-signed certificates are not supported. Instead, sign your certificate with a Certificate Authority (CA).
- Ensure that the SAS® Web Server points to the full certificate chain file. For more information, see the topic "Configuring SAS Web Server Manually for HTTPS" in the SAS® 9.4 Intelligence Platform: Middle-Tier Administration Guide or the topic "Encryption: Data in Motion" in the SAS Viya Administration Guide.
- Alternatively, install the client certificate, all intermediate CA certificates, and Root CA certificates on your device. For information about how to install certificates, refer to the documentation for your mobile device. This will have to be done for any device that needs access.
- Ensure that the Root Certificate Authority appears in the list of installed certificates on your device. For information about where to find the list of installed certificates, refer to the documentation for your mobile device.
- (iOS only) Ensure that all installed certificates are listed as Trusted or Verified on your device.
Operating System and Release Information
SAS System | SAS Mobile BI | Apple Mobile Operating System | 7.1 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Date Modified: | 2020-05-11 07:27:20 |
Date Created: | 2014-10-15 09:31:19 |