Teamwork Cloud 18.5

Versions Compared

Old Version 5

changes.mady.by.user Mimi Sari Kurnia

Saved on

compared with

New Version Current

changes.mady.by.user Developer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To enable SSL on the TWAdmin's Server Settings page

You can enable the secure connection option on the Server Settings page of the TWAdmin. This page also allows you to disable the option if you do not need to use a secure connection (see the following figure). You can always enable it whenever working on a confidential document or information or whenever necessary. 

 To To enable a secure connection using the SSL protocol in TWAdmin


  1. Click . The Server Settings page will open (Figure 1). 

    Figure 1: The TWAdmin's Server Settings page.

  2. Click  to enable the SSL protocol. The SSL option will be enabled (in green).

    Figure 2: Enabling SSL protocol on the TWCloud server (when the option is turned on, the color will change to green).
  3. Input the port, select a Java Key Store file by clicking , and type the password.
  4. Click .

 

At this point, you will be able to use MagicDraw to connect to TWCloud via the SSL connection. 

 

Warning
titleSelf-signed SSL certificate warning

Teamwork Cloud Admin (TWAdmin) uses SSL (Secure Socket Layer) as the security protocol to keep any information you enter on TWAdmin private and secure.

By default, your server generated an SSL certificate and signed it as being valid (self-signed certificate). The self-signed SSL certificate allows a secure connection to be established, but does not verify the authenticity of the server like the SSL certificate issued by a valid Certificate Authority (CA) does.

Trusted root certificates are embedded into popular browsers such as Internet Explorer, Firefox, and Chrome. They are used to verify all SSL certificates that the browsers encounters. If a certificate is not signed by one of these roots, the browsers will display an error or warning message stating that it is untrusted. Therefore, when you are trying to access the server via the self-signed one, you will get the error or warning in your web browser. Figure 3 shows the example of the "SSL certificate not trusted" warning in Chrome.

 

Figure 3: A self-signed SSL certificate error in Google Chrome.

 

This warning is letting you know that the SSL certificate installed on your server was self-signed and cannot be verified by the browser. You may simply let your browser accept it and continue using the server. If you are using Firefox, you can accept it and the error or warning will no longer appear. If you are using Chrome, the error or warning will appear every time you try to access your server.

 

To permanently mitigate this situation so that you will not have the self-signed SSL certificate error or warning when accessing your server via SSL, it is recommended that you either:

  • Replace the self-signed SSL certificate with a dedicated one issued by a trusted certificate authority.
  • Establish your own root certificate authority and manually import it to each browser on all workstations.