Minimum Product Requirements and Support for Running NEO

These are the minimum requirements for running NEO with optimal performance. If your devices, systems, or networks do not meet these requirements, your experience may be degraded. 

Check the current release notes for updates to this information. Any updates to this information will be first published in the NEO Release Notes.

End-user Requirements

Operating SystemWindows 10 or Windows 11 (preferred)
Browser Requirement
  • Chrome (For NEO 3.9, certified on version 119.0.6045.160)
  • Microsoft Edge (For NEO 3.9, certified on version 120.0.2210.91)
RAM4GB of RAM
DisplayGraphics resolution 1366 X 768 or better
Internet Connection

For optimal performance, ONE recommends that users have a bandwidth of no less than 30mbps (download) with no greater than 10ms latency. ONE leverages a CDN (Akamai) with edge caching to reduce latencies globally. The application is still functional with reduced speed of as low as 10mpbs (download) and latency as high as 20ms - however this results in significantly degraded performance. Speeds slower than these thresholds are not recommended.

Requirements for System-to-System Integration

Oracle Client Requirements

When integrating directly with ONE's legacy Data Warehouse (Valdero):

  • Oracle Client compatible with oracle 12
MariaDB Client Requirements

When integrating directly with ONE's Data Warehouse (including Enterprise Slice and/or Enterprise Data Warehouse): 

  • MariaDB CLI requires MariaDB-client(10.4.18)
  • MariaDB GUI using JDBC requires MariaDB Java connector 2.4.0

Additional details can be found at:

SFTP RequirementsWe support Password Auth and Key Auth. We use SSH2 protocol.
AS2 Integration Requirements

A Trading Partner is required to provide ONE with the following:

  • AS2 profiles for Production and Test environments by filling out the AS2 onboarding spec forms provided by ONE.
  • Certificates for Production and Test AS2 connections.
HTTPS Integration Requirements

Compatible with TLS 1.2, and TLS 1.3.

Compatible with SNI.

Supported cipher suites (accurate as of January 2023; subject to change):

  • TLS 1.3 (Suites in server-preferred order)
    • TLS_AES_256_GCM_SHA384
    • TLS_CHACHA20_POLY1305_SHA256
    • TLS_AES_128_GCM_SHA256
    • TLS_AES_128_CCM_8_SHA256
    • TLS_AES_128_CCM_SHA256
  • TLS 1.2 (suites in server-preferred order)
    • TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
    • TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
    • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    • TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
    • TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
    • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
    • TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
    • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
    • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
    • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
    • TLS_RSA_WITH_AES_256_GCM_SHA384
    • TLS_RSA_WITH_AES_128_GCM_SHA256
    • TLS_RSA_WITH_AES_256_CBC_SHA256
    • TLS_RSA_WITH_AES_128_CBC_SHA256
    • TLS_RSA_WITH_AES_256_CBC_SHA
    • TLS_RSA_WITH_AES_128_CBC_SHA
SAML

SAML 2.0 is supported for federated authentication

Language Support

NEO supports the localization of menus, labels, error messages, alerts and emails.
The following languages are supported by NEO:

  • English (US)
  • Spanish (Mexico)
  • French (Canada)
  • Portuguese (Brazil)
  • Chinese (Simplified)

For concerns or questions please contact: [email protected]