Overview
TickeTrak offers two methods for clients to establish a direct connection to their hosted database: ODBC (Open Database Connectivity) and IPSec (Internet Protocol Security). These options enable data extraction for reporting and integration with external systems. However, direct modifications to the database are strongly discouraged, as they can compromise system stability.
Choosing the Right Connection
Tables can't be imported directly. Please insert an image of your table which can be found here.
Feature
ODBC
IPSec
Security Level
Moderate
High
Ease of Setup
Easy
Complex
Best For
Reporting & analytics
Secure system integrations
Network Requirements
Open firewall rules
VPN/IPSec tunnel setup
If security is your primary concern, IPSec is the recommended choice. If you prefer a simpler setup, ODBC may be more suitable.
Option 1: ODBC Connection
What It Does:
- Enables querying and extracting data from the database.
- Works with reporting tools like Excel, Power BI, and SQL-based applications.
- Allows integration with third-party applications requiring database access.
Limitations & Risks:
- Direct database modifications are not recommended due to potential system issues.
- Performance may be impacted by inefficient queries.
- Security relies on network configurations and access controls.
Technical Requirements for ODBC Setup
To establish an ODBC connection, please provide the following information:
- List of all external IP addresses that will be used for the connection.
- Firewall access: Your IT team must allow traffic to 146.20.176.67 on port 1433.
- SQL login credentials: A database login must be created for ODBC access.
- ODBC configuration: The ODBC driver must be installed and configured on workstations that need to connect to 146.20.176.67 on port 1433.
Option 2: IPSec Connection
What It Does:
- Creates a secure, encrypted tunnel between your network and TickeTrak’s hosted database.
- Ensures secure data transmission for integrations and reporting.
- Reduces exposure to unauthorized access.
Limitations & Risks:
- Requires IT expertise to configure and maintain the VPN.
- Encryption may introduce minor performance overhead.
Technical Requirements for IPSec Setup
To configure an IPSec tunnel, please provide the following details:
- IKE Version: IKEv1 or IKEv2
- VPN Device Details: Manufacturer and model number
- Public IP Address: Peer address for the VPN device
- Encryption Domain: Your remote IP(s) or network(s) that will communicate via VPN
- Encryption & Authentication Settings:
- Phase 1 Encryption Algorithm: AES-128/192/256
- Phase 1 Hash Algorithm: MD5, SHA1, SHA256, SHA384, SHA512
- Phase 1 Diffie Hellman Group: 2, 5, 14, 19, 20, 21
- Phase 1 Pseudorandom Function (PRF): MD5, SHA1, SHA256, SHA384, SHA512
- Phase 1 Lifetime (seconds): 86400 or 28800 recommended
- Pre-Shared Key:
- IKEv1: Custom password of your choice
- IKEv2: Pre-Shared Key (secure transmission required)
- Phase 2 Security Settings:
- Encryption Algorithm: AES-128/192/256
- Hash Algorithm: MD5, SHA1, SHA256, SHA384, SHA512
- Perfect Forward Secrecy (PFS): Enabled? If so, specify DH Group (2, 5, 14, 19, 20, 21)
- Phase 2 Lifetime (seconds): Preferably lower than Phase 1
Next Steps
Once we receive the required information, our team will coordinate with your IT department to complete the setup. If you have questions or need guidance, please contact our support team at support@cardinaltracking.com.