Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author alexacrm

    (@alexacrm)

    @jandigital

    nothing’s wrong with app id & secret. That’s, unfortunately, a small bug that we need to fix. Good news is that there is a workaround:

    • Switch back to username/password auth, fill in the details with anything but specify correct URL.
    • Press Connect – it will fail
    • Switch back to OAuth 2.0/Shared Secret auth and complete the fields
    • You should be able to connect now.

    Let me know if it didn’t work for you.

    I am having the same issue on our site. The above steps aren’t working please help.

    Plugin Author alexacrm

    (@alexacrm)

    @sawancontractor can you be a bit more specific?
    What is not working? What message do you receive and at what point?
    Have you created app user in Dataverse?
    Have you granted this user sufficient permission?

    Yes, We’ve done this. I am using your pro version and this is on our client website. Is there anyway to process this request quickly please?

    Unable to connect to Dynamics 365: cURL Error: 6, Could not resolve host: XRMServices. Check whether you selected the appropriate deployment type and that CRM URL and credentials are correct.

    Plugin Author alexacrm

    (@alexacrm)

    @sawancontractor if you’re using pro version then for urgent assistance please email [email protected] with the account details (either registration email or license key)

    I’ve just sent an email on that email. Thanks,

    How long roughly do you think they will take to respond?

    Plugin Author alexacrm

    (@alexacrm)

    @sawancontractor we are trying to assist as soon as we can. The email advising of the protocol deprecation has been sent about 3 weeks ago but right now we’re experience an influx of support calls from the customers atttempting to implement the change at the last minute. Sorry about the delays.

    Thread Starter jandigital

    (@jandigital)

    Hi,

    There was no bug, it was human error on my end. I typed in the Secret ID instead of the Secret Key – FYI for those trying. The links I shared and the instructions do work.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Dynamics 365 OAuth 2.0 Not Working – Authentication’ is closed to new replies.