Technical Specifications • One (1) Physical Network Connection • Two (2) Network Interface Cards (NIC) • DHCP or Static IP Address • DNS • Outbound Internet Access • TCP: 443 (Web Traffic for Kiosk) • UDP: 1194 or TCP: 443 (VPN Traffic for Key Box) • UDP: 123 (NTP Time Synchronization) • OpenVPN Connect v3 or higher • IP Forwarding Enabled in Windows OS Other Specifications • DNS must be able to resolve agilefleet.com and any of its subdomains. • Outbound internet must allow access to agilefleet.com and any of its subdomains and openvpn.com and any of its subdomains. • The first NIC is required for the LAN connection, and the second NIC is required to connect the key box to the kiosk. A USB based network adaptor may be used if a second NIC is unavailable. • DHCP is preferred, but a static IP address can be used. The IP Address, Subnet Mask, Default Gateway, and DNS address information is required for the static IP option. • UDP: 1194 is the default protocol the VPN client installed on the kiosk. The VPN client will automatically fallback to TCP: 443 if UDP: 1194 is unavailable. • The default NTP source is time.windows.com • Data Channel Encryption: • Algorithm: AES (Advanced Encryption Standard) • Key Length: 256 bits • Mode: CBC (Cipher Block Chaining) Control Channel Encryption: • Protocol: TLS (Transport Layer Security) • Key Exchange: RSA-2048 • Session Key Exchange: Diffie-Hellman (DH) or Elliptic Curve Diffie-Hellman (ECDH) for Perfect Forward Secrecy (PFS) • Cipher Suites: AES Message Authentication: • Algorithm: HMAC (Hash-based Message Authentication Code) • Hash Function: SHA256 KioWare license to support controlled presentation of the kiosk user interface Functional Requirements Upon login, the user’s reservation should be immediately available for dispatching and key disbursement/return Integrated kiosk functionality must include the ability to display the following information to the user at the time of check-out before the key is released Reservation confirmation number Scheduled leaving and returning date and time Current leaving date and time Vehicle name Parking space Current odometer Vehicle year, make model Fuel level Optional vehicle equipment Upon vehicle return, the kiosk must automatically present the returning vehicle confirmation details to the user and include the ability to capture the following minimum details Current vehicle return date and time Current odometer Fuel level Parking location Comments Provide an option to allow any user to return the keys to a vehicle Provide optional RFID/employee badge access
