Not ready

Hi @jmfarber,

Could you give me some details on what’s happening? Others are successfully authenticating with the new plugin and it was tested extensively, so I’m confident we can get you working as well.

Please note we don’t “open new cases” with Pardot Support from this forum. You are welcome to contact them separately.

As soon as I get more details, I can help. I also recommend trying the standard Pardot authentication if you’re having trouble with the new SSO process.

Getting the same error as others – error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration

Thanks, @jmfarber. You’re right that a couple of people have seen this error, but we’ve yet to confirm it’s an issue with the plugin.

Have you confirmed the callback URL In your Salesforce connected app exactly matches the URL of the Pardot settings screen?

Add the hosting IP address to the trusted Ip addresses.

Created a connected app
Used the following call back URL – https://securis.com.com/wp-admin/options-general.php?page=pardot

Pardot Scope

Copied the two keys into the settings –

Get the following error

error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration

Also, you have little to no documentation on how to set this up. As I said it’s not ready.

also creating a case with pardot will mean it will get resolved sometime in Q4.

@jmfarber Your feelings about support and documentation are duly noted. I’m an individual attempting to help you personally.

Regarding your issue, is ‘https://securis.com.com/wp-admin/options-general.php?page=pardot’ a typo in this post? If not, that’s likely the issue. Make sure the connected app doesn’t have “.com” twice.

The downgrade doesn’t work either. We are now officially screwed.

Callback URL
https://securis.com/wp-admin/options-general.php?page=pardot

that is copied from the connected app.

I don’t see a typo.

New error which I guess is a good thing.

We can’t authorize you because of an OAuth error. For more information, contact your Salesforce administrator.

OAUTH_APPROVAL_ERROR_GENERIC : An unexpected error has occured during authentication. Please try again.

I’m not sure if my experience with the plugin last evening may be of assistance here or not.

We had a situation where upon the release of 1.5, my client’s authentication ceased to be valid. The error message was that the account was locked out due to too many failed login attempts. At which point our embedded forms would not display and in fact seemed to cause a php error. I do not have that error code as our production system is on an AWS Elastic Beanstalk deployment.

We tried to update the credentials, and could not get the site to re-authenticate using 1.4.13 (I think. It was the immediate release version to 1.5) The error was that the “email was not available for authentication.” I eventually clicked the button “Reset all settings” and the site went down. We could not navigate to either the WP dashboard to the public facing site because of an error.

I restored the database backup from our nightly backup and got the site restored and then attempted to troubleshoot in a development environment.

I then updated the plugin in my dev environment and re-entered my credentials using the Pardot Authentication type (Which was only now available after the update and was able to connect.

There are two things that come from this for me:
1) the error seems to be related to the API itself not accepting backward compatible requests smoothly. Perhaps they were supposed to be routed somewhere differently or whatever, but that seemed to fail for our connection under the 1.4.13 version.
2) trying to completely reset the settings for the Pardot configuration was further missing error catching that brought down our site.

I don’t know if this helps troubleshoot this particular issue, but it seems to have some bearing to me.

@tworowstudio Thank you for the help. The rest of our site is working fine. It’s just the pardot plugin.

@cliffseal Any suggestions or should i create a case.

Thanks for the input, @tworowstudio! That sounds like an issue a prior update addressed, but some folks needed to manually delete a couple of database rows in the options table. Other support topics should point you in the right direction—otherwise, just open a new ticket here and I’ll help.

@jmfarber If your admin can’t help troubleshoot that error, then yes, I recommend opening a ticket. I’m more than happy to help make updates to the plugin if we can isolate an issue with it, but that error doesn’t allow us to do that, unfortunately.

Again, I recommend using direct Pardot authentication instead of Salesforce SSO for now if that’s possible for you. You don’t have to downgrade to get to that.