CRM api authentication issues

Hi @barry,

Just to confirm, were you able to add the OAuth 2.0 Web Service in Tools > FME Options> Web Connections > Manage Services or is the 404 error only appearing in the translation log?

Helpful Resources:

• Creating Web Connections
• FME Options: Web Connections

No i was not; i did notice that option for the http caller but not in the odata reader. Thanks @chrisatsafe i will try to figure that out from your links. I'll look to the Microsoft dynamics 365 option for starters unless you can point me to the correct web service to use for active directly. Its actually CRM 2016's api that i'm trying to get at.

Awesome, I'd start with the web service and see if you get the same login window when you enter the registered apps info (i.e. client id, secret, etc.). When you scroll to the bottom of the web services parameters you should see a Test button which will open an authentication window where you can enter your credentials.

ok so getting close; i figured out how to add the OAuth 2.0 web service and i can login, but its not clear to me how set up the parameters. Getting stuck here: After the authenticate i'm simply inside CRM in the popup window.

Hmm, okay. I also just found a web connection for this on the hub: https://hub.safe.com/publishers/safe-lab/web-connections/microsoft-dynamics-365

There are steps on the hub page that mention what you need to have setup, might be worthwhile just checking the list and downloading the web connection to see if that does the trick!

Ya; its not 365 so that is not going to do it. I think my issue is with the oauth2 parameters. Is there any documentation or examples that could be provided to help me out here? I am able to login, but then is no different the using the CRM application via the web browser. I'm missing something for sure. thx again for your help so far!

Overall, resolving authentication issues can be tricky, but ensuring that FME is configured correctly with the appropriate authentication method and credentials should help resolve the 401 errors.

It sounds like you're encountering some authentication issues while trying to extract data via the CRM API. It can be frustrating dealing with 401 errors, especially when you know the authentication should be working fine. I've had similar experiences with API integrations in the past, and sometimes the issue lies in the configuration or permissions settings.

Have you double-checked the authentication credentials you're using in FME? It might be worth verifying that the credentials are correctly set up and have the necessary permissions to access the CRM API.Additionally, considering you can successfully query the API using a web browser after authentication, it seems like the issue might be specific to how FME is handling the authentication process. Have you tried reaching out to their support team for assistance? They might be able to provide some insights or troubleshooting steps to help resolve the issue.As for the ODATA reader authentication problem, it could be related to the same underlying issue. Sometimes, switching between different authentication methods or tweaking the configuration settings can resolve such issues.Overall, dealing with API authentication issues can be tricky, but with some patience and perseverance, you'll likely be able to find a solution. And hey, if you're still struggling, maybe get a monday free trial from some company. Sometimes trying out a different tool or platform can provide a fresh perspective and help you overcome the challenge.