Overview
Who will be impacted?
Next steps
Feature comparison
Migration steps

Overview

With the release of the new and improved LogMeIn app integration (built and maintained by LogMeIn) featuring SAML and SCIM provisioning functionality, Okta is officially ending support for the app integrations listed below on 2/28/20. After 2/28/20, the deprecated app integration(s) in your Okta environment will continue to exist and function. However, Okta will no longer provide updates or support for these apps, which include the following:

• GoToTraining SAML 

• RescueAssist* or Service Desk

• GoToWebinar 

• GoToMeeting 

• OpenVoice 

• GoToAssist (Seeit) 

GoToAssist Remote Support is now RescueAssist

The new LogMeIn app integration is your one-stop shop to enable SAML and manage users for all the LogMeIn products listed above (and more). It offers enhanced functionality, and a better user experience by allowing you to set up SAML at an organization level, and push groups and members to the LogMeIn Admin Center. The new LogMeIn app integration will allow LogMeIn to add any future enhancements, so customers are encouraged to upgrade at their earliest opportunity. 

Who will be impacted, and what is the impact?

If you use LogMeIn apps and have one or more of the following OIN app integrations active in your org with the following default names, you will be impacted (note that you might have changed this default name when configuring the app in your org):

• GoToTraining SAML 

• RescueAssist or Service Desk

• GoToWebinar 

• GoToMeeting 

• OpenVoice 

• GoToAssist (Seeit) 

*GoToAssist Remote Support is now RescueAssist

After 2/28/20 Okta will no longer investigate or fix bugs for the app integrations listed above. You may continue to use these integrations after the EOL date; however, be mindful that Okta will only provide support for technical issues found in the new LogMeIn app integration.

Next Steps

• Budget at least 1-2 weeks for the project, including planning, testing, and rollout.

• Review the migration documentation below to understand the available SSO and Provisioning functionality.  

• Set up and test the new LogMeIn app integration available in the Okta Integration Network.

• Migrate all users to the new LogMeIn app integration before the EOL date.

For questions about the EOL Okta integration(s) for LogMeIn products, contact Okta support at https://support.okta.com. For questions about LogMeIn products themselves, the new LogMeIn app integration, or the migration process, contact LogMeIn support at https://support.logmeininc.com/contactus.

Feature Comparison

Before you Begin

• If you plan to set up SCIM provisioning with the new LogMeIn app as part of the migration, please note the following:

  • new users are created in the LogMeIn Admin Center only after being added to a Group that has already been assigned to the app and pushed. Pushing users without a group membership is not supported.

  • Deactivating a user means removing the user’s account role and product access. The user will not be deleted from the LogMeIn account but will instead remain assigned a “Suspended” status in the Admin Center.

  • Before you can configure provisioning for LogMeIn, you must set up an “organization” by registering at least one valid email domain with LogMeIn to verify your ownership of that domain.

• If applicable, read the SCIM provisioning guide to understand the steps involved to set up the LogMeIn SCIM app Integration.

• If applicable, read the SAML configuration guide to understand the steps involved to set up the LogMeIn SAML app Integration.

• The LogMeIn app Integration tile is used to configure SAML and SCIM functionality. SWA SSO is for LogMeIn ID; you can optionally add separate Child Applications to provide single sign-on access for end-users directly in to the LogMeIn products.

Migration Steps

We recommend setting up SCIM provisioning before configuring your desired sign-on mode. The Provisioning Migration Steps are applicable to the following sets of customers:

1. Customers migrating from the GoToMeeting provisioning app integration to the LogMeIn SCIM provisioning app integration

2. Customers migrating from the EOL SSO app integrations listed above, but wish to enable and use the LogMeIn SCIM provisioning app integration

I. Prerequisites (Note: This section is applicable to provisioning and SAML. If you are migrating to SWA only, this is optional for you; skip to SWA SSO Migration steps)

The new LogMeIn application is designed to work with groups and not with individual users. Users cannot be pushed to LogMeIn without a Group Membership, so you need to:

1. Create the required groups in your Okta organization for separate LogMeIn products. Refer to the SCIM or SAML guide for details.

LogMeIn_GoToMeeting

LogMeIn_GoToTraining

LogMeIn_GoToWebinar

LogMeIn_OpenVoice

LogMeIn_RescueAssist

2. Assign desired users to appropriate groups (LogMeIn products)

NOTE: One user can be assigned to multiple groups (LogMeIn products).

3. Add the LogMeIn application to your Okta organization. (If you are migrating SWA only, refer to the SWA SSO migration steps section. The LogMeIn app integration SSOs into LogMeIn ID, and not the products. You will need to use the child applications to configure SWA SSO into the individual products)

4. Select Do not display application icon to users and Do not display application icon in the Okta Mobile app on the General application tab.

5. Make sure that the "Application username format" value on the Sign On tab in the new LogMeIn application matches the "Application username format" in the existing application.

II. Provisioning migration steps.

Note for Okta admins who use the GoToMeeting provisioning app integration: The GoToMeeting provisioning app integration supports provisioning new users and assigning those users only to the GoToMeeting product in LogMeIn. In comparison, the new LogMeIn SCIM provisioning app integration supports provisioning new users to the LogMeIn Admin Center and can assign memberships to all LogMeIn products, including GoToMeeting. Access to the LogMeIn products depends on the user's Group memberships.

1. Follow the steps outlined in the SCIM Configuration Guide to enable provisioning for the LogMeIn app Integration.

2. As a reminder, remember to:

   1. Push groups created in the prerequisites section of this guide to the application.

   2. Assign appropriate groups to the corresponding LogMeIn products in LogMeIn.

   3. Provision new / link existing users to the app.

III. SAML SSO migration steps.

1. Assign Okta groups from the prerequisites to the new LogMeIn app Integration application.

2. Follow the SAML 2.0 Setup instructions located on the Sign On application tab in order to:

   1. Add LogMeIn Child Applications (instructions here).

   2. Configure LogMeIn Parent Application (instructions here).

3. Assign required groups created in the prerequisites section of this guide to the corresponding child applications.

IV. SWA SSO migration steps.

1. For SSO into LogMeIn ID, use the LogMeIn app Integration. If this is the app you wish to use for SWA SSO, de-select Do not display application icon to users and Do not display application icon in the Okta Mobile app on the General application tab to make it visible on end-users dashboards.

2. For SSO in to each of the LogMeIn products, use the following new Child Apps:

   1. GoToMeeting

   2. GoToWebinar

   3. GoToTraining

   4. OpenVoice

   5. RescueAssist

   6. GoToAssist Seeit

3. Under the single sign-on tab, select a desired option.

4. Assign users or groups created in the prerequisites section of this guide to the corresponding child applications.

5. Reach out to end-users and have them copy and paste their username/password from the old tiles to the new tiles made available on their dashboards.

V. Test the new LogMeIn applications

1. SAML: Check if SP-initiated SSO works correctly for LogMeIn products.

2. SWA & SAML: Check if child apps (SWA and/or SAML) work correctly.

3. SCIM Provisioning: Check if new/existing users have been pushed to LogMeIn successfully and assigned to the correct LogMeIn products.

VI. Deactivate and delete the old apps:

1. Open the old application(s) in the Administrator UI in Okta.

2. For GoToMeeting provisioning app integration, go to the provisioning tab and turn off provisioning.

3. Select Deactivate, then select Delete.