Procedure

1. Configure Web Central server to work with HTTPS/TLS. See http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html .
2. Configure the computer where Smart Client is installed by installing the Web Central server security certificate for the current user. See https://support.securly.com/hc/en-us/articles/206081828-How-to-manually-install-the-Securly-SSL-certificate-in-Chrome

3. You can now start Smart Client and use the URL of the Web Central server, for example: https://localhost:8443/archibus/.

For the production deployment, you should consider using chain trust versus peer trust. See in How To: Create and Install Temporary Certificates in WCF for Message Security During Development in http://wcfsecurity.codeplex.com

If Using Microsoft .Net 4.5 and Later

Smart Client supports the TLS security protocol of Microsoft .Net 4.5 and later. If you have not installed .Net 4.5, you cannot use TLS 1.2.

If you are using this version, configure the Web service and set the special flag in SmartClient config .

1. Check the configuration file SmartClient.Common.dll.config
2. Find the section <Settings />
3. Find the field SecurityProtocol
4. Set the selected version of TLS.

Example of the <Settings> section:

<Settings
InstallationType="Full"
Locale="en-US"
Username="AI"
Password="f@y^*-m1357902468a ZXw=+"
DefaultAppServerLocation="http://localhost:8080/archibus/"
LocalDrawingFilesFolder="C:\Users\Public\Archibus\projects\my-drawings"
DefaultProject="HQ-Sybase-WebEdition"
RememberCredentials="true"
SecurityProtocol="Tls12"
>

If you receive the error message "incorrect format of configuration file" after changing SecurityProtocol to TLS1.2 ( SecurityProtocol="Tls12" ), make sure that you have the right setting according to the .NET version used.

For examples of TLS versions:

• Tls
• Tls11
• Tls12 (base protocol TLS 1.0; protocol TLS 1.1 and TLS 1.2)

see https://msdn.microsoft.com/en-us/library/system.security.authentication.sslprotocols(v=vs.110).aspx

Troubleshooting