GoToWebinar Authentication doesn't work anymore | Community
Skip to main content
Michael_Florin-2
Level 10
July 14, 2026
Question

GoToWebinar Authentication doesn't work anymore

  • July 14, 2026
  • 1 reply
  • 60 views

Two of our GTW integrations are showing errors:

 

 

The standard procedure of double clicking that line, hitting “Log Into GoToWebinar” just redirects to a Marketo login page. Even if we are logged in that GTW account. Anyone seeing that too and knowing a trick? Did something change on the GTW side?

Thanks!
Michael 

    1 reply

    Level 3
    July 14, 2026

    This may be unrelated to GTW. We encountered the same issue with Zoom, and clearing the active session allowed it to load successfully.
    Based on what we learned, cross-site cookies/tokens are used during the LaunchPoint handshake, and active browser sessions can sometimes cause this looping behavior.
    It may be worth trying the same approach here!

    Found this helpful? Mark the thread as solved so other community members can quickly locate the answer.
    Michael_Florin-2
    Level 10
    July 15, 2026

    Could you describe your procedure in detail, please? I tried everything with regards to clearing session, incognito mode, changing browsers, deleting cookies - no change.

    Level 3
    July 15, 2026

    Hi ​@Michael_Florin-2 

    In my case, the issue was resolved by completely logging out of both Marketo and Zoom, then logging back into Marketo and reauthorizing the LaunchPoint service.

    If that doesn't resolve the issue, Adobe Support mentioned that this type of behavior can be more complex than a simple session reset. They recommend capturing the browser's network activity during the authorization flow. This helps determine whether the problem is with the LaunchPoint redirect itself or with the provider's OAuth authorization/token exchange.

    You can capture a HAR (network) file using your browser's Developer Tools while reproducing the issue and share it with Adobe Support. That information should help them identify where the authorization flow is failing.

    Hope this helps!

    Found this helpful? Mark the thread as solved so other community members can quickly locate the answer.