New authentication works on dev subdomain but not on production domain

  • Resolved jscheytt

    (@jscheytt)


    7 years ago

    Hello there,

    we use the [gotowebinar-reg key=…] shortcode on several pages on our site. I upgraded to version 12.1 on a dev environment (subdomain.production.site) and established the new app API connection in the dev backend (clicking the button in the “General Options” tab). I saw it worked on dev, so I upgraded the plugin on the production environment (production.site) too, but the plugin fails there in several ways:

    1. An error message (something along the lines of “The webinar no longer exists or has been removed”) is displayed instead of the registration form OR
    2. The registration form is displayed but after submitting, an error message about “Attendee limit reached” or so is shown (which is not true).
    3. Either of these problems happens on some of the sites with a [gotowebinar-reg] shortcode, but not with all of them.

    After re-authenticating in the production site backend 1 – 3 times in a row, all pages with the shortcode work again. This holds for maximum about 24 hours, then the errors described above appear again. (I wonder if the last point could be related to our deployment: We currently overwrite dev with production every 24 hours. But even after deactivating this procedure, the errors keep re-appearing.)

    The shortcodes on the dev environment however work flawlessly all the time (as far as I can see).

    I wonder if this problem could be due to the fact that I connected your app with our GoToWebinar account from the subdomain and not the production domain. I tried to find a way to revoke your app’s access to my account to then authenticate again from the production domain, but GoToWebinar support said it is currently not possible to revoke app access at all.

    Do you see a way of handling this problem? We currently downgraded to 12.0 as there still is some time until 14th of August (the announced OAuth forcing date).

    Best regards,
    jscheytt

Viewing 1 replies (of 1 total)
  • Plugin Author Northern Beaches Websites

    (@northernbeacheswebsites)

    Hi @jscheytt,

    I sent an email to my pro users which I believe covers what you are describing. Please see below:

    As a consequence of this update, if you are in a situation where you may use the plugin on a staging or development site and then have another instance of the plugin in production, you can no longer share authentication details to connect to the 1 GoToWebinar account. For 2 reasons, firstly the authentication details are no longer visible in the plugin settings so you can’t practically do it anyway, but more importantly, because of this new authentication system even if you could share details you would be continually booting yourself off authentication from one site to the next so you will need to be continually re-authenticating which isn’t practical. There’s no awesome solution to this unfortunately. All I can advise is to either just have 2 GoToWebinar accounts, one for development and one for production, or once a site is pushed to production to disable the plugin on the development server and re-authenticate the plugin again in production.

    So the issue has to do with GoToWebinar’s new authentication measures and I can’t get around this. What is likely happening is that your development environment is booting your production site off authentication. The reason the webinars might have worked in production for 24 hours is probably due to the fact that the cache works for 24 hours and then gets automatically cleared after this time (so it can be a bit of an illusion). I recommend just for testing purposes turning off the cache and then clearing the cache and then testing things out (but I do strongly recommend turning the cache on again after things are worked out for performance and quota reasons).But yes have only one version of the plugin going at any one time.

    Thanks,

Viewing 1 replies (of 1 total)
  • The topic ‘New authentication works on dev subdomain but not on production domain’ is closed to new replies.