Open Collective
Open Collective
Loading
Update 1: JD Ops Authorization successful!
Published on July 23, 2023 by Greg Austic

Summary

There is a successful process to authorize a FarmOS instance to access data from a JD Ops organization.  The process is fairly easy though not perfect - it is easily set up by our team and could be set up by any farmOS / JD Ops user with some effort.  We identified a better process but have decided to pursue that after these first two phases are complete based on need.  Some data has been gathered through this authorization flow, and it looks reasonably similar to FarmOS data, making us hopeful that the next step of saving that data will be reasonable.  The process of actually saving the data from JD Ops in FarmOS needs more review and consideration to get right in the next phase.

Developers Updates

  • Project updates:
  • Dev updates:
    • We have authorization + authentication working with JD! After an “application” is created in JD, users can “connect” farmOS to their JD account and allow access to their JD org

  • Demo/testing:
    • Greg - please test the following steps keeping in mind:
      • Intentionally making this a little vague to see if it is easy to follow
      • Think about the language & button text, does this make sense & is it consistent with what you see in JD (IMO JD might be a little *inconsistent* with how they refer to app/connections/organizations, what do you think?)
    • Test steps:
      • Go to JD settings in farmOS and configure the client:
        • Client ID: add ID
        • Client secret: add secret
    • Connect farmOS to your JD Account
    • Determine if farmOS has access to your JD Organization
      • If it does not have access, add a connection from JD org -> farmOS
      • If it does have access, modify the connection in JD, and verify that farmOS updates
      • Repeat! So you see both cases. (Greg, Mo is using your account so it may start with already having access, I do not know.)
    • Reset the integration so farmOS is not connected to your JD Account
  • Next steps:
    • Add offline/refresh token flow
    • Ability to select which JD organization you are connecting to this farmOS instance
    • A couple bug fixes
    • Address feedback here re: authentication + authorization flow