Skip to main content
Michael_Florin-2
Michael_Florin-2
Level 10
July 14, 2026
Question

GoToWebinar Authentication doesn't work anymore

  • July 14, 2026
  • 7 replies
  • 131 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 

    7 replies

    Adobe Champion
    adesrala1Adobe Champion
    Adobe Champion
    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
    Michael_Florin-2Author
    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.

    Adobe Champion
    adesrala1Adobe Champion
    Adobe Champion
    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.
    polvera
    Level 1
    August 28, 2026

    Did you resolve the issue ​@Michael_Florin-2? I’m encountering the same problem. 

    Michael_Florin-2
    Michael_Florin-2Author
    Level 10
    August 30, 2026

    Yes. Here’s the grande finale of my long discussion with Gemini:

     

    The Diagnostics

    When you clicked "Log into GoToWebinar," GoToWebinar's authorization server successfully authenticated you and redirected your browser back to Marketo with a valid authorization code (the payload in your URL).

    Instead of consuming that code and showing you a "Success" screen, your browser sent the token to Marketo, but Marketo's security system rejected the transfer. Because the transfer failed, Marketo treated your session as unauthenticated and immediately booted you back to the main login portal.

    This is a SameSite cookie / CORS protection issue that modern browser engines are heavily enforcing. Even in standard Incognito mode, browsers block HTTP POST or redirect callbacks that transfer state across different domains (from goto.com to marketo.com).

    How to Bypass the Redirect Block

    Since the browser's security layers are aggressively blocking the redirect token, you need to use a method that prevents the browser from realizing a cross-site handshake is occurring.

    Method 1: The "Different Browser Engine" Fix (Easiest & Most Successful)

    If you are doing this in Chrome or Edge (Chromium-based), their identical underlying security architectures will block this.

    1. Open Firefox or Safari (if on a Mac). If you don't have Firefox installed, it is highly recommended to download it just for this administrative task.

    2. Open a Private/Incognito window in that secondary browser.

    3. Turn Off any built-in tracking prevention (in Firefox, click the shield icon next to the URL bar and toggle "Enhanced Tracking Protection" to Off for these sites).

    4. Log into Marketo and complete the Launchpoint connection. Why this works: Firefox handles the isolation of parent windows and OAuth pop-up iframe redirects differently than Chromium, which usually allows the token callback to pass without triggering the login redirect.

     

    I can’t say if any of this is true, but I turned off Tracking Protection in Firefox and then I could actually authenticate.

    Terms & ConditionsAccessibility statement

    Loading footer...