@kejo take a look at this thread and see if it has a resolution for you?
Thread Starter
kejo
(@kejo)
Thank you Jonathan – I tried that thread and no luck.
I checked the Database and it does create the two tables you mentioned.
I also tried troubleshooting the following suggestions you made:
1. Re: Disabling JavaScript- I disabled Javascript in the browser and I could confirm that there was a a string after the code variable in the URL before the redirection happens. How do I verify if it’s the correct code parameter?
2. Re: JavaScript error somewhere- Not seeing any JS errors in the console.
3. Re: mismatched setting somewhere: I have verified the settings as best as I can for the Consumer Key, Consumer Secret, Call Back URL, Login Base URL. I was able to connect to using a REST client and a PHP script with these settings as well.
4. Re: PHP errors – no PHP errors in log.
My feeling is that it is either a server setting on my end or something that needs to be configured in SF? Any further thoughts?
@kejo I think you should also check the permissions for the app in Salesforce. One person on that thread said the following:
Hey you guys, I had the same issue. You were right in that it was a permissions error. I check the url after clicking the authorize button and it said the user does not have permission to access this app. I went into my permissions and searched for the app I created in SF and then added that app to my permissions. Viola.
Hopefully it’ll be that easy.
Thread Starter
kejo
(@kejo)
Hi Jonathan –
I wasn’t 100% sure what was meant by Permissions in that response but the API Scope had been set for Full Access which I had assumed would cover all the options but once I added these two scope the connection worked:
Access and manage your data (api)
Perform requests on your behalf at any time (refresh_token, offline_access)
Thanks for your help and quick responses.
@kejo great. Yes, those are definitely the required permissions. We have that in the documentation, but it’s unfortunate that we don’t have a way to check the app from the plugin side so we could notify in a more usable way. Glad it worked.
