[Notification] We're upgrading the JumpCloud Support Center the week of September 30th.

Support Center

Single Sign On (SSO) with GoToMeeting

Important: This article contains out-of-date information. For current application information, see Connecting Applications with JumpCloud Using Pre-Built Connectors.


  • Generate a public certificate and private key pair.
  • In order to successfully complete the integration between JumpCloud and GoToMeeting, you must use an administrator account in GoToMeeting.
  • If your connector was built prior to 1/26/18, either delete and recreate it - OR - open the existing connector and select save to apply the new template, then re-edit correct the URLs that have changed due to the merger with LogMeIn.


  • How to configure User authorization.
  • GoToWebinar, GoToAssist, GoToTraining, and OpenVoice share a SAML endpoint with GoToMeeting. If you would like to use these connectors, you must use the same private key for each of these connectors.

Configure the JumpCloud SSO Application

  1. Access the JumpCloud Administrator Console at https://console.jumpcloud.com.
  2. Select Applications in the main navigation panel.
  3. Select the + in the upper left, scroll or search for the application in the 'Configure New Application' side panel, the select 'configure'.
  4. You can upload a service provider application's XML metadata file to populate SAML connector attributes for that application. The attributes populated by the metadata file may vary by the application. To apply a metadata file for the application you're connecting, click Upload Metadata. Navigate to the file you want to upload, then click Open. You'll see a confirmation of a successful upload. Be aware that if you upload more than one metadata file, you'll overwrite the attribute values applied in the previously uploaded file.
  5. In the IDP Entity ID field, enter https://YOURDOMAIN.TLD (e.g., https://thebestwidgets.com).
  6. Select Upload IdP Private Key and upload the private.pem file generated according to the above prerequisites.
  7. Select Upload IdP Certificate and upload the cert.pem file generated according to the above prerequisites.
  8. In the SP Entity ID field, enter https://authentication.logmeininc.com/saml/sp.
  9. In the ACS URL field, enter https://authentication.logmeininc.com/saml/acs.
  10. In the Default RelayState field, enter https://global.gotomeeting.com.
  11. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  12. (Optional) In the Display Label field, enter a label that will appear under the Service Provider logo within the JumpCloud User console.
  13. Select Activate.

Configure the Service Provider

  1. Log in to https://myaccount.logmeininc.com/ as an administrator.
  2. Select on the Identity Provider tab.
  3. Select Manual from the configuration dropdown.
  4. In the Sign-in page url field, enter the same IdP URL that you set in the JumpCloud console (if you did not modify the termination of this URL, then enter the default URL: https://sso.jumpcloud.com/saml2/gotomeeting).
  5. For the Sign-in binding, select the POST radio button.
  6. In the Identity Provider Entity ID field, enter the IDP Entity ID used above.
  7. In the Verification certificate field, select Upload certificate and upload your public certificate.
  8. Select Save.

Validate SSO authentication workflows

IdP Initiated

  • Access the JumpCloud User Console at https://console.jumpcloud.com.
  • Log into the JumpCloud User Console as a user configured for SSO in your GoToMeeting account.
  • Select the Service Provider icon.
  • This should automatically launch and login to the application.

SP Initiated

  • In your Web browser, navigate to your GoToMeeting login page.
  • Select Use my company ID.
  • Enter your GoToMeeting account's email address, and select Continue.
  • If necessary, log into the JumpCloud User Portal.
  • You should be logged into GoToMeeting.

Last Updated: Aug 20, 2019 09:28AM MDT

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found