Hi guys,
I am currently developing an integration to pull data from Acumatica ERP. I am trying to implement an OAuth 2.0 flow using the Authorization Code Flow.
From reading through the resources, I have gotten this flow to work for my local Acumatica ERP instance. However, I am struggling to understand how to expand this to other Acumatica ERP instances, such as those used by our clients.
I understand that a key part of the OAuth flow is creating a record in the Connected Applications form, and being issued a Client ID and a secret. I’ve seen that I can export this Connected Applications form as part of a Customization Project, but when I import this Customization Project in another Acumatica ERP instance, it loses the record in the Connected Applications form. I suspect this may have to do with the tenant name being different in the other instance, but I am unsure how to get around this.
Even if I do get this Customization Project approach to work, it doesn’t seem logical to me to have each of my clients import this project in order for me to be able to kick off the OAuth process with them. Is there a step that I’m missing somewhere? Does this process differ in production environments?
Any advice would be appreciated.
Thanks,
Jonah
Best answer by Dmitrii Naumov
View original