Server Manager Settings

Configure SSL, certificates, and secure endpoints by modifying Server Manager Settings.

**Users upgrading to PlanetTogether Version 11.49.x and later will need to also upgrade to Instance Manager version 12.0.57 or later. In addition, users will need to generate or set a certificate in the Server Manager settings for services to work properly (see Certificate Settings section below). 

 

**It is recommended that users set a signed certificate if possible.  When using signed certificates, there is no need to set a thumbprint on the Sign-In application.

The Server Manager Settings can be accessed from the Instance Manager ribbon.

General Settings

Server Settings

  • Enable Compatibility Connections: If this is checked, Port 7990 will be hosted when running older versions of PlanetTogether. However, this port should not be used for new installations (versions 11.43.x and later) as Port 7991 is the most secure port. You can leave this box unchecked when using PlanetTogether versions 11.43.3 and later.
  • Host Legacy Services: This must be set to true to run PlanetTogether versions 11.48.x and older and to use PlanetTogether APS Sign-In apps version 4.1 and older.
    • This can be disabled once a certificate is generated and the instance manager is restarted (see Certificate Settings section below).
    • If this is set to False, then Version 4.4 of the PlanetTogether APS Sign-In app must log in with PlanetTogether Version 11.49.3 and later versions. If you wish to use older versions (4.1 and older) of the PlanetTogether sign-in app with PT versions 11.49.x and later, this option must be set to True.

Certificate Settings

**PlanetTogether versions 11.49.x and Instance Manager versions 12.0.57 and later require a certificate.  If you do not have a certificate, you will need to generate one.

**You must select or generate a certificate for services to work properly.

** Some older versions of Windows may fail to try to generate a certificate.  You will need to generate one manually in this case.  From a PowerShell instance with administrative privileges, enter:

New-SelfSignedCertificate -KeyLength 2048 -KeyAlgorithm RSA -DnsName [your DNS name] -Type SSLServerAuthentication -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.1") -FriendlyName [certificate name]

Example:

New-SelfSignedCertificate -KeyLength 2048 -KeyAlgorithm RSA -DnsName PlanetTogether.local -Type SSLServerAuthentication -TextExtension @("2.5.29.37={text}1.3.6.1.5.5.7.3.1") -FriendlyName PlanetTogether

  1. Click on "Generate Certificate."
  2. You will see a "Success" message popup. Click "OK." If you do not see a success message, you may need to follow the steps in the region above.
  3. You should see "Secure connection is being enforced" under the "Certificate Settings" section.
  4. **If the certificate was manually generated, you must copy the Certificate Thumbprint and follow the steps below.
  5. Click "Save and Close."

Additional steps for manually generated certificates. These steps will not be needed if the chosen certificate is valid.

  1. Open the PlanetTogether Client.
  2. Click on "Options."
  3. Paste the copied Certificate Thumbprint (from step 4 above) in the text box.

  4. Change or create a new connection string specifying "https" and the new SSL Client port (default:7994). Note: You can find the appropriate SSL Client Port in the
    Server Manager Settings | General Settings.


 

Server Message

Administrators can set a global message that will be displayed upon client login.

  1. Open the Instance Manager.
  2. Click the "Server Manager" button.
  3. Go to the "Server Message" tab and type in the message to display to all users.
  4. When users open the PlanetTogether Client (APS Sign-In) application, the message will be displayed: