AGRIS Customer Documentation

AgLogic - Pro Dispatch - Support updated connectivity via OAuth2 standards (AGS-23284)

Benefits

Enhanced data exchange security between Agroguide and Aglogic.

Description

Effective March 31, 2024, John Deere will implement token based authentication to access Pro Dispatch (AgLogic). Token authentication replaces User / Password authentication during data exchange between Agroguide and Aglogic. Token authentication uses a combination of authorization ids to exchange data between Agroguide and Aglogic. Authorization ids include John Deere provided Application Id and Secret, and a Refresh Token. For each transaction the authorization ids are used to generate a unique transaction access token. Token authentication does not change the data processing business rules.

CFT Operations Center Pro Dispatch Configuration

Communications > Operations Center Pro Dispatch > Operations Center Pro Dispatch Configuration

The first configuration screen is used to assign authentication ids necessary to exchange data between Agroguide and AgLogic.

  • URL (Required): URL, also known as John Deere Base Path URL, is the access point to Pro Dispatch site. The URL is pre-assigned in the default configuration file, but should be verified with John Deere.

  • Application ID and Secret (Required): Identifies your Pro Dispatch organization profile. Application ID and Secret are provided by John Deere and are encrypted in configuration file.

  • Refresh Token (Required): John Deere assigned token needed to access the Web Service. Once all authentication ids are assigned and saved, the user may get or update Refresh Token from the Refresh Token input form. Process will display John Deere log in form. Enter the id and password used to access the AgLogic site. Log in form will automatically close after Refresh Token is downloaded.

    • Recommend setting Chrome as the default browser. Other browsers may require user to manually close browser after retrieving Refresh Token. All open browser sessions must be closed prior to retrieving token.

    • Refresh Token will expire if it has not been used within 365 days from issue. Expired tokens may be updated through Refresh Token input form.

  • Authorization URL (Required): Is the OAuth 2 well-known URL established by John Deere and used to verify access to Pro Dispatch site. The URL is pre-assigned in the default configuration file, but should be verified with John Deere.

  • Callback URL (Required): Is the local URL used to verify access to Pro Dispatch site. Set URL to localhost with port number designated in your Pro Dispatch organization profile. Default port number, 9089, may be changed based on local network requirements.

  • State (Required): Additional security value to prevent cross-site forgery. Replace "test state" with text you designate.

  • Scope (Required): Pro Dispatch data permissions. Use pre-assigned scope.

  • Domain (Optional): Set Domain if needed for accessing the Web Service.

  • Local Proxy (Optional): Set Use Local Proxy to Y if a local proxy is required. Proxy settings may be configured under the Utilities->Document Tracking->Setup option.

  • Earliest Business Date (Required): Specifies the oldest Blend Releases that you
    care to communicate to Pro Dispatch.

 

image-20240315-191752.png

 

 

image-20240315-195805.png

 

CFT Operations Center Pro Dispatch Configuration Setup Guide

  1. Create John Deere Pro Dispatch Application Profile

    1. Contact John Deere to sign authorization agreement and support setting up profile

    2. Make sure John Deere sets Application Details - Application Status to “Production”

    3. Make sure Security - Redirect URI is set to local host port. The Redirect URI is assigned to AGRIS CFT Operations Center Pro Dispatch’s Callback URL. The Redirect URI and Callback URL must be the same. The CFT default value is http://localhost:9089/callback. Port number may be changed.

    4. If organization requires identifying accessible web sites, work with internal IT department to include CFT configuration URL and Authorization URL.

    5. Stop AGRIS job stream running Pro Dispatch (aka AgLogic).

    6. Log on to AGRIS database machine. User that logs on must have administrator rights to machine. Recommend logging on directly to machine and not through remote desktop.

    7. Verify Google Chrome or Microsoft Edge is installed on machine. Preference is to use Google Chrome. Microsoft Edge may require user to manually close browser during Refresh Token authorization. Google Chrome is not required for data exchange between AGRIS and Pro Dispatch and may be uninstalled after acquiring Refresh Token.

    8. Run AGRIS in administrator mode.

    9. If necessary apply AGRIS CFT license and Operations Center Pro Dispatch extended option.

    10. Select CFT - Communications - Operations Center Pro Dispatch menu option.

    11. Select Option 1 - Configuration (Step 1). Update Application Id, Secret, and Callback URL with values assigned to John Deere profile. Profile Redirect URI value is assigned to Callback URL. Change State “test state”. For example, your company name.
      ** Firewalls / Web Security: If necessary white list URL and Authorization URL to allow communication with Pro Dispatch.
      Save configuration and exit back to AGRIS main form.

    12. Select Option 1 - Configuration (Step 2 - Refresh Token). Select Refresh Token grid line and click Get/Update Refresh Token button. John Deere sign on web page will appear. Enter Username and Password authorized to access Pro Dispatch site. User and password may be different than the user and password used to access John Deere profile. After login, web page will close and the Refresh Token will be assigned to configuration grid. Save configuration. You are now ready to complete remaining configuration settings, Integration, Date Time, Location Code and Communication Log.



       

 

3820 Mansell Road, Suite 350 ✦ Alpharetta, GA 30022 ✦ www.GreenstoneSystems.com
© 2011 - 2024 Cultura Technologies LLC. All Rights Reserved Worldwide.  Products and company names mentioned herein may be trademarks or registered trademarks of their respective owners.