Discussions
Categories
Oracle Eloqua Alert : Action required for GoToWebinar App
Important: We are introducing a more reliable way to use the GoToWebinar app by leveraging client specific connected app. This requires customers to add their own connected app credentials in the application configuration for GoToWebinar App by 31st Dec 2018. The current configuration without Connected app would no longer be supported after 31st December 2018 which may result in disruption of services.
Overview
GoToWebinar app requires a connected app for the integration. Currently, Oracle Eloqua uses a global configuration for accessing the integration which sometimes results in limit errors and integration not working as expected. We have already made an enhancement to give the ability to add site specific GoToWebinar connected app. To make the integration more reliable, we require all sites to use their own connected app going forward.
All customers are required to add their own GoToWebinar connectedapp credentials in the application configuration for normal services to work as expected.
What’s Changing
The GoToWebinar app uses a connected app for the integration. Currently, if you do not have your own app credentials in the Application Configuration, it leverages Oracle Eloqua’s default connected app. We are advising customers to use their own site specific GoToWebinar connected App in Oracle Eloqua’s application configuration for GoToWebinar.
The site specific Connected app for GoToWebinar applications provides customers more handle on the rate limits, since they can directly work with GoToWebinar teams to increase them as required.
Next Steps
As a next step, to make the integration more reliable, we are advising customers have their own site specific connected app.
Step 1: Create site specific connected app, working with your GoToWebinar representatives as required. Here is the support link to refer that. For additional information, refer to GoToWebinar's documentation.
Step 2: Add the newly created connected App into the application config of the GoToWebinar Application before 31st December 2018. For additional information, refer to our documentation.
FAQ
Q: Why do I need to add the Connected App, my Integration is working fine?
A: Adding a site specific connected app makes the integration more reliable, as rate limits are not shared across sites. Customers also have an added benefit of increasing their limits based on their usage. Simply stating, this will minimize rate limit errors.
Q: What happens if I do not add Connected App by 31st December 2018?
A: If the site specific connected app is not configured by December 31st, 2018, the GoToWebinar services will stop working for that site.
Q: How do you create a connected App for GoToWebinar?
A: Refer to GoToWebinar's documentation.
Q: How do I add the connected App inside the App Configuration?
A: Refer to our Oracle Eloqua Help Center.
Comments
-
TIP:
After you connect your Connected App to the GoToWebinar app, you'll need to reauthorize credentials.
However, re-authorization won't work if you have the wrong redirect on your GoToWebinar developer app.Within Eloqua, go to Settings < My Apps < GoToWebinar < Configure Icon
Then within the "Citrix GoToWebinar Registration Configuration" popup window, there are three icons in the top right (home, question, info).
Click on the info icon - this is where you'll find the App Url --> use this url as the redirect when you create the GoToWebinar developer app.
Now you can reauthorize your credentials in Eloqua!
-
TIP:
After you connect your Connected App to the GoToWebinar app, you'll need to reauthorize credentials.
However, re-authorization won't work if you have the wrong redirect on your GoToWebinar developer app.Within Eloqua, go to Settings < My Apps < GoToWebinar < Configure Icon
Then within the "Citrix GoToWebinar Registration Configuration" popup window, there are three icons in the top right (home, question, info).
Click on the info icon - this is where you'll find the App Url --> use this url as the redirect when you create the GoToWebinar developer app.
Now you can reauthorize your credentials in Eloqua!
In the GoTo app, it has consumer key and consumer secret but in the credentials part of the config window it has App Name and App Key...
Do I put in the consumer key and the secret of the app in GoTo into the credentials part of the Eloqua config window?
Post edited by Unknown User on -
In the GoTo app, it has consumer key and consumer secret but in the credentials part of the config window it has App Name and App Key...
Do I put in the consumer key and the secret of the app in GoTo into the credentials part of the Eloqua config window?
Hi Katie,
Within Eloqua in the GoToWebinar configurations, "Connected App Credentials"
App Name = whatever you want
App Key = GoTo Consumer Key (no need to combine it with the secret)
Hope that helps.
Nhan
-
Will there be an update for using OAuth 2.0 of the GoToWebinar API? The legacy OAut (Version 1) will be shutdown on October 1st in 2019. Legacy OAuth is already disabled for newly created GoToWebinar apps.
See:
https://status-goto-developer.logmeininc.com/incidents/86dq0zvdkqmg
-
Will there be an update for using OAuth 2.0 of the GoToWebinar API? The legacy OAut (Version 1) will be shutdown on October 1st in 2019. Legacy OAuth is already disabled for newly created GoToWebinar apps.
See:
https://status-goto-developer.logmeininc.com/incidents/86dq0zvdkqmg
@René Lücking Did you hear anything about an update for OAuth 2.0 of the GoToWebinar API? We are getting alert emails from LogMeIn and they pointed me back to Eloqua since it's for Eloqua's app.
-
Will there be an update for using OAuth 2.0 of the GoToWebinar API? The legacy OAut (Version 1) will be shutdown on October 1st in 2019. Legacy OAuth is already disabled for newly created GoToWebinar apps.
See:
https://status-goto-developer.logmeininc.com/incidents/86dq0zvdkqmg
I'm running into the same issue when trying to reauthorize my accounts in the Eloqua App configurations:
"{"error":"OAuth API v1 has been decommissioned as announced in February 2018, please switch to OAuth API v2 documented here: https://goto-developer.logmeininc.com/oauth-migration-guide. Please reach out to Support ([email protected]) with questions."}
-
I'm running into the same issue when trying to reauthorize my accounts in the Eloqua App configurations:
"{"error":"OAuth API v1 has been decommissioned as announced in February 2018, please switch to OAuth API v2 documented here: https://goto-developer.logmeininc.com/oauth-migration-guide. Please reach out to Support ([email protected]) with questions."}
What we ended up doing was creating a new GoTo connected app & reauthenticating with the new app. It didn't cause any harm to the webinar steps on canvases so perhaps that is an option to try.
-
Hello-
I am new to Eloqua so I thank you in advance for your patience.
I am trying to set up this integration and noticed the tip above had me go into the app set-up and grab the URL there, but the documentation (https://docs.oracle.com/en/cloud/saas/marketing/eloqua-user/Help/Apps/GoToWebinar/Tasks/InstallingGoToWebinarApp.htm) has me add what seems to be a more general URL for our pod. In the LogMeIn dev site, you can have more than one so I just have both. What is the difference between the two or is there any harm in having both?
