We will be undergoing scheduled maintenance during this time.
Aug 22, 15:11 UTC
Scheduled for Jan 31, 00:00 - Feb 01, 00:00 UTC
Update: While most integrations migrated successfully to TLS 1.2 as of today, we decided to further extend support of legacy TLS 1.0 and TLS 1.1 protocols to acknowledge the ask for more time to migrate customers to the updated versions of the integrations.
Nevertheless, we strongly recommend migration of your integrations and customers from the deprecated and insecure TLS 1.0 or TLS 1.1 to the new TLS 1.2 standard as soon as possible.
NOTICE: This date was pushed back-- it was previously scheduled for October 31, 2018.
The LogMeIn GoTo API is depreciating support for TLS 1.0 and 1.1 for all HTTPS connections.
Starting on January 31, 2019 TLS 1.2 will be required when making a connection to any GetGo API URLs.
What should you do for uninterrupted logins?
* Verify your customers use TLS 1.2-compatible versions of their browsers.
* Verify the software (such as automation tooling) connecting to the GetGo API service supports TLS 1.2.
If you have any questions, please contact Support. We apologize for any inconvenience this may cause and appreciate your support.
Aug 2, 15:43 UTC
The initial posting listed the end date as January 19, 2019. This has been updated to reflect the correct date.
Jul 26, 16:26 UTC
Starting on January 31, 2019, the LogMeIn GoTo API will enforce the strict OAuth 2.0 authentication protocol to improve security of our API program. This change requires your action.
The new OAuth 2.0 protocol is available and can be used immediately. Updated LogMeIn GoTo SDKs supporting the new OAuth 2.0 protocol have been published.
Support for the old protocol will end on January 31, 2019 to give you time to test and update your code to use the new authentication services available under https://api.getgo.com/oauth/v2
This change affects the following APIs: GoToMeeting APIs, GoToWebinar APIs, GoToTraining APIs, GoToAssist APIs, GoToAssist SeeIt APIs and related Administrative APIs. The GoToAssist Corporate APIs are not impacted by this change.
Please review the OAuth Migration Guide for details. Please direct any questions to firstname.lastname@example.org
Our number one priority continues to be delivering great service and a best-in-class experience to you. We are here to help should you have any questions!
Jul 26, 13:19 UTC