This configuration is required to enable the use of the SmartAdvocate mobile app, the
from an out of network location, SmartAdvocate’s mobile application, texting integration, and other integrations.
To enable remote access to the SmartAdvocate application server, the following are necessary:
An IP address and port capable of reaching the server.
Depending on the existing configuration of your network, this address may either be the public
address of the server itself, or of the router or other device which forwards from a specific port to a
port on the server. Either configuration is compatible with all SmartAdvocate functionality. If you
are using port-forwarding, the two ports can be the same or different.
...
A DNS entry mapping a hostname on your domain to the IP address in the previous section.
Many firms create an “sa” subdomain for this purpose, so that the hostname is similar to
“sa.example.com.” This is not required – any valid hostname will work – but may be easy for your
users to use and recognize.
An SSL certificate corresponding to the chosen hostname.
See https://www.sslshopper.com/how-to-order-an-ssl-certificate.html for a summary of how to
order an SSL certificate. SmartAdvocate does not offer any particular recommendation as to which
SSL provider you should use. Remember to create the certificate request (CSR) from IIS on the
SmartAdvocate application server itself so that it can successfully be completed on that server.
If you already have a wildcard SSL certificate elsewhere on your network, it is likely possible to use
that certificate for the SmartAdvocate application server. You may need to re-key it for the server;
your SSL provider should be able to provide specific instructions.
If you already have a hostname and SSL certificate on the SmartAdvocate application server (e.g., if
it is already running another externally-accessible application), it is not necessary to create an
additional DNS entry or certificate for SmartAdvocate; the existing ones can be used.
An HTTPS binding for the web site in IIS.
Once the certificate has been installed in IIS, open the server node, then the Sites node, then select
Default Web Site and click Bindings... in the Actions pane. (If SmartAdvocate has been installed
under a site other than the Default Web Site, select that site instead; however, in nearly all
instances, SmartAdvocate is installed under the Default Web Site.)
...