oAuth error; Missing parameters redirect_uri and scope

Hey weptile,

Can you please clarify where you are in the set up process? HubSpot has dropped support of oAuth 1.0, and as such, you need to update to version 3.0.0 or later of our plugin, which supports oAuth 2.0

Our new update requires SSL and PHP 5.5 at a minimum.

If you’ve already updated to the latest version of the plugin, and it still has issues, please go to Forms > Settings > Hubspot, and copy the link that the “Click Here to Authenticate” button contains, and email it to me at [email protected]

DO NOT paste it here, as it does contain sensitive information. However, it would look something like this:

https://app.hubspot.com/oauth/authorize?client_id=CLIENT_ID&scope=forms%20contacts&redirect_uri=https%3A%2F%2Fmyurl%2Fwp-admin%2Fadmin.php%3Fpage%3Dgf_settings%26subview%3Dgravityforms-hubspot%26trigger%3Dhubspot_oauth

This ticket was resolved via email. we’ll be pushing a bug fix up for a couple of minor PHP errors, but for the purposes of this thread, things are fine ??

Hello,

I had the same problem. Reintegrated, updated and re-authorized everything, but the integration is still working. The leads are coming in, but the plugin is not sending them Hubspot. Please help!

Does our website really need an SSL certificate in order for this plugin work now?

MerchantCapital,

Yes, it is a requirement on the part of HubSpot’s oAuth 2.0 integration.

Arguably it doesn’t actually need an SSL cert. As long as the server properly accepts the SSL path to the same location as your non-secured website, you could pass by without one. But that is 1) a bad idea, 2) not secure, which is the entire point, and 3) Google provides higher ranking for sites with SSL certificates these days, so if you don’t have one, you really should get one.

Related to HubSpot, not us, though: https://developers.hubspot.com/docs/methods/oauth2/initiate-oauth-integration … see screenshot for the specific requirement: https://puu.sh/xgwSj/ac6a2a5fde.png

As for you having the same issue as weptile, I did receive your email, and you look like you’re using the right authentication URL (though your redirect URL is pointing to a dev site?)…

In the end, without any changes, Weptile tried the link again, and it worked. Perhaps it was browser caching, but I find that unlikely.