Forum Discussion
Solved
Azure SSO Problems
Hi there,
I know it's been a while since you raised this issue, BUT I am getting the exact same error trying to configure LogMeIn SSO with Azure AD. I have reached out to LogMeIn support (uns...
This is a combination of DWilliams14 comments for anyone else having an issue with this:
"For anyone else having this issue, I was able to resolve it by changing the identifier URL in the Azure AD App.
By default it is https://authentication.logmeininc.com/saml/metadata/sp and the instructions say not to change it, but changing it to https://authentication.logmeininc.com/saml/sp fixed this error for me - this is the url that they say to use if you look at the generic instructions for setting up SAML manually instead of the Azure specific ones.
The generic instructions for 'Custom Enterprise Sign-In Configuration' that you linked are fine. However the instructions for Azure AD specifically are not. If you look at this article: https://support.logmeininc.com/central/help/set-up-enterprise-sign-in-sso, under step 2 follow the link for Azure AD which takes you here: https://learn.microsoft.com/en-us/entra/identity/saas-apps/logmein-tutorial
On that page, under 'Configure Microsoft Entra SSO', step 5 says "On the Basic SAML Configuration section, the user does not have to perform any steps as the app is already pre-integrated with Azure."
However, the app default setting for entity ID is "https://authentication.logmeininc.com/saml/metadata/sp" which is incorrect. Within the azure app while configuring, it also tells you to use that incorrect url in the tooltip."
Hi vitalyb, welcome to the community.
I noticed you commented on an old GoToMeeting thread, but you are actually a Central customer so I have moved your post to the Central community. I see that your support ticket was escalated and we are currently waiting for feedback from the development team.
Hi - I'm encountering the exact same error when trying to set up SSO with Azure AD. I used the automatic configuration and when I test from the Azure AD side, it seems to work. But if I try to log into GoTo with my company credentials, I get the error listed above.
