Integrate LogMeIn with Identity as a Service
LogMeIn provides cloud-based remote work tools for collaboration, IT management and customer engagement (see https://logmein.com). You can protect access to LogMeIn by integrating LogMeIn with Identity as a Service. Once integrated, users can use single sign-on to log in to their LogMeIn account through Identity as a Service.
Note: This integration was tested using Identity as a Service version 5.15 and LogMeIn Admin Center v.5.29.0. Other versions of LogMeIn may require integration and configuration steps that differ from those documented in this procedure. For other versions of LogMeIn, this integration guide may be used as an initial approach for integrating LogMeIn. In the event of other issues, contact support@entrust.com for assistance.
Prerequisites
Before you begin, you need to configure a LogMeIn domain. See https://support.goto.com/meeting/help/enterprise-sign-in-g2m790099
To integrate LogMeIn with Identity as a Service, you must do the following:
Step 1: Add LogMeIn to Identity as a ServiceStep 1: Add LogMeIn to Identity as a Service
Add LogMeIn as an application to Identity as a Service
Log into your Identity as a Service administrator account.
Click 
> Security > Applications. The Applications Lists page appears.
Click Add. The Select an Application Template page appears.
Do one of the following:
Select SAML Cloud Integrations from the search drop-down list and scroll to find the application you want to add to IDaaS.
- or -
In the Search bar, enter a search option to filter for the application you want to add to IDaaS.
Click LogMeIn. The LogMeIn page appears.
Enter an Application Name.
Enter an Application Description.
Optional. Add a custom application logo.
Click 
next to Application Logo. The Upload Logo dialog box appears.
Click 
to select an image file to upload.
Browse to select your file and click Open. The Upload Logo dialog box reappears showing your selected image.
If required, resize your image.
Click OK.
Select the Authentication Flow that appears to users during login.
Click Next. The General page appears.
In the Default Assertion Consumer Service URL field, enter:
https://authentication.logmeininc.com/saml/acs
In the Service Provider Entity ID (Issuer) field, enter:
https://authentication.logmeininc.com/saml/sp
In the Single Logout Service URL field, enter:
https://authentication.logmeininc.com/saml/SingleLogout
Optional. Enter the SAML Username Parameter Name used to identity the user ID being requested for authentication. The user ID can then be passed as a parameter, for example, Username=jdoe. Alternately, if the SAML username is NameID, the SAML Request XML NameID element value is used to the identify the IDaaS userID.
Enter the SAML Session Timeout to the time when the SAML Assertion times out. The maximum is 720 minutes.
Enter the Max Authentication Age (seconds) to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
From the SAML NameID Attribute drop-down list, select Email.
From the SAML NameID Encoding Format drop-down list, select Email.
From the SAML Signing Certificate from the drop-down list, select the signing certificate.
From the SAML Signature Algorithm drop-down list, select SHA512.
Select Sign Complete SAML Response.
Deselect Enable Go Back Button if you do not want users to be able to go back to the LogMeIn login page to log in.
Select Show Default Assertion Consumer URL Service in the My Profile. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
Optional. Add Alternative Assertion Consumer Service URLs, as follows:
Click Add.
Enter a Name.
Enter a URL Value.
Select Show in My Profile to display the Alternative Consumer Service URL in a user's My profile page.
Optional. Add an Application Logo.
Click Add.
Repeat these steps to add more Alternative Assertion Consumer Service URLs.
Relay states appear on the user's My Profile page.
To add a relay state (this example shows adding a relay state for GoToMeeting):
Under Relay State, click Add. The Add Relay State dialog box appears.
Enter GoToMeeting in the relay Name field.
Enter the Value for the relay state. This setting specifies the application or URL that a user is redirected to after successful authentication. For GoToMeeting, enter
https://global.gotomeeting.com
Click Add.
Repeat these steps to add the URLs for any of the following:
GoToMeeting – https://global.gotomeeting.com
GoToWebinar – https://global.gotowebinar.com
GoToTraining – https://global.gototraining.com
OpenVoice – https://global.openvoice.com
GoToAssist Remote Support – https://up.gotoassist.com
GoToAssist (Service Desk) – https://desk.gotoassist.com
GoToAssist Remote Support v5 – https://console.gotoassist.com
GoToConnect – https://my.jive.com
Bold360 and Boldchat – https://launch.bold360.com/
Notes: After you add relay states, you can also enable or disable them on the Add/Edit application page. Click 
next to the relay state to disable it or click 
to re-enable it.
Relay states apply to the Default Assertion Consumer Service URLs and not the Alternative Consumer Service URLs.
Click Submit.
Step 2: Add a resource ruleStep 2: Add a resource rule
Step 3: Download the metadata from Identity as a ServiceStep 3: Download the metadata from Identity as a Service
Download the Metadata file from Identity as a Service
In Identity as a Service, click > Security > Applications. The Applications List page appears.
Do one of the following:
Click 
next to the application you are integrating with Identity as a Service.
–or–
Click 
next to the application you are integrating with Identity as a Service and select SAML IDP Metadata.
The SAML Application Metadata dialog box appears.
Select the certificate to include in the SAML IDP Metadata file from the drop-down list.
If applicable, Select the domain to include in the SAML IDP Metadata file from the drop-down list.
Enter the Lifetime, in days, for the SAML IDP Metadata file. The value must be between 2 and 730.
Do one of the following, as required:
Copy the Public Endpoint to paste into your SAML application being used Identity Provider authentication.
Click Download.
Note: If you are using multiple domains, you must download each domain's metadata file separately because the values in the metadata file vary for each domain.
Step 4: Configure LogMeIn for Identity as a Service authenticationStep 4: Configure LogMeIn for Identity as a Service authentication
Configure LogMeIn for Identity as a Service single sign-on
Log in to your LogMeIn administrator account, for example, your GoToMeeting administrator account. The Hub page appears.
Click your account menu and select My profile. your Personal Info page appears.
Click Sign In & Security.
Under Enterprise Sign In, click Edit Company.
Click Identity Provider. The Identity Provider page appears.
From the How would you like to configure your SAML IDP? drop-down list, select Upload SAML metadata file.
Click Upload metadata file and browse to upload the file you downloaded in Step 3: Download the metadata file from identity as a Service.
Click Save.
Click Save on the confirmation prompt.
Step 5: Test the integrationStep 5: Test the integration
Testing Service Provider Login
Open a Web browser and enter the URL for your LogMeIn account. You are directed to Identity as a Service.
Enter your LogMeIn account User ID and click Next.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to LogMeIn.
Testing Identity as a Service redirect log in
Log in to your Identity as a Service account.
Go to your My Profile page if you are not already there.
Under Applications, click LogMeIn.
Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to LogMeIn.