Security & Platform Governance TTSFX NEXUS SOFT
TTSFX NEXUS SOFT: Security & Platform Governance
Personal engineering documentation, database schemas, authentication logic, device fingerprinting, and operating procedures for the TTSFX NEXUS SOFT engine.
TTSFX NEXUS SOFT: Security & Platform Governance documentation detailing multi-tenant recruitment architecture, hybrid identification login logic, hardware device fingerprinting, four-color candidate lifecycle engines, and automated PesaPal paywall integration.
🛠️ Technical Navigation
- Section 1: System Capabilities & Architecture Overview
- Section 2: Core Database Schema & Data Pipeline
- Section 3: Hybrid Authentication & Multi-Identifier Resolution
- Section 4: Workstation Binding & Hardware Fingerprint Security
- Section 5: Brute-Force Defense & Password Recovery Logic
- Section 6: Subscription Integration & Paywall State Engine
- Section 7: Developer Operations & Troubleshooting Guide
1. System Capabilities & Architecture Overview
I built TTSFX NEXUS SOFT as a multi-tenant operational and financial management software engine. It is engineered to handle organization registration, secure user authentication across multiple roles, hardware device tracking, automated billing passes, and branch-level data isolation. The platform provides end-to-end data processing for high-volume recruitment, international manpower agencies, and cross-border candidate lifecycle tracking. By consolidating disjointed office spreadsheets, employee mobile chats, and physical paper files into a single centralized database environment, TTSFX NEXUS SOFT eliminates operational latency and data loss across distributed operational branches.
1. "I see your agents are stressed using personal phones to talk to clients. When a recruit asks about their visa at 9:00 PM, nobody answers. With TTSFX Nexus, our AI handles those night-time questions, sorts your candidates into Blue, Amber, and Green pools, and gives your 20 staff members one professional dashboard to manage everything. No more lost messages, no more complaints."
2. "Stop letting your business run on your employees' personal WhatsApp. If an employee leaves today, they take your clients with them. With TTSFX Nexus, you own the data, the AI handles the midnight questions, and you can see exactly who is in the Amber Pool waiting for a visa."
Core Engineering Capabilities:
- Multi-Tenant Architecture: Complete logical separation of data across different master agencies, their sub-branches, and staff accounts. Database level isolation guarantees strict privacy and prevents cross-agency data exposure during queries.
- Hardware Security Layer: Custom client fingerprinting that binds user sessions to specific physical workstations, preventing unauthorized remote access or credential sharing on personal devices outside official office terminals.
- Multi-Identifier Input Engine: Flexible login interface capable of resolving standard usernames, staff emails, corporate admin handles, and agency emails automatically without administrative intervention or pre-selected dropdowns.
- Integrated Paywall & Gateway: Built-in subscription expiration interceptor backed by automated PesaPal payment processing (supporting MTN MoMo, Airtel Money, and Card transactions) for real-time account renewal.
- Self-Healing Recovery: Automated email token dispatch and dynamic PIN verification system for password resets without direct database intervention or manual admin intervention.
- Market Integration: Engineered to track candidate journeys end-to-end, serving as a lifetime management system from initial recruitment in Kampala to overseas deployment across global destinations.
The 4-Stage "Lifecycle" Engine:
To maintain systematic visibility over thousands of active applicant files, TTSFX NEXUS SOFT organizes every record into a structured four-stage color-coded processing state machine:
- Registration (Blue): New clients and job applicants actively enrolling. Raw contact details, preliminary background checks, and initial intake metrics are captured and indexed.
- Processing (Amber): Candidates fulfilling mandatory deployment requirements, paying document fees, undergoing medical evaluations, and awaiting official embassy visa issuance. Automated milestone alerts notify agents of pending documents.
- Transit (White): Candidates with successfully issued visas awaiting scheduled travel dates, flight ticketing confirmation, and mandatory pre-departure orientation protocols.
- Field Ops / Abroad (Green): Active workers deployed overseas requiring continuous 24/7 welfare support, contract monitoring, emergency tracking, and remote helpdesk communication throughout their contractual tenure.
By enforcing this color-coded lifecycle state engine, organizational leadership can immediately audit active operational bottlenecks across any branch location with zero manual reporting overhead.
2. Core Database Schema & Data Pipeline
The underlying database architecture is designed for multi-tenant efficiency, speed, and strict relational integrity. Key foreign relationships enforce cascading updates and restrict unauthorized data leakage between separate commercial entities using relational scoping filters (`agency_id`, `branch_id`). Every database transaction executes within transactional boundaries to guarantee atomic integrity across complex operations.
EXAMPLE: Agency A signs up, logs in, and initiates a subscription (either a free trial or active plan). For optimal setup and testing, we recommend starting with the 7-day free trial to configure system connections.
After logging in, navigate to the Nexus Connection section in our service menu to configure your remote database connection details. Before inserting credentials, send us a quick message detailing your setup requirements on our support line.
When establishing remote database connections or bridging external branch nodes, the software enforces secure cryptographic handshakes using asymmetric RSA key pairing alongside AES-256 session encryption. This prevents payload snooping or packet sniffing across public networks.
3. Hybrid Authentication & Multi-Identifier Resolution
To prevent user login friction and eliminate login errors across diverse user roles, I engineered the authentication pipeline to accept multiple identifier formats through a unified, single input field. Users do not need to specify their role or identifier type beforehand; the authentication controller parses, normalizes, and resolves incoming strings dynamically.
How Input Resolution Logic Operates:
- Sanitization: The system automatically strips leading and trailing whitespace and converts the incoming input string to lower case (e.g.,
Admin@Agency.comis normalized toadmin@agency.com). - Sequential Lookup: The server evaluates the identifier against database user indices in exact optimized sequence:
username(Standard operator handle)email(Individual staff email address)corporate_email(Master agency administrative account)
- Password Verification: Once the target account record is successfully located, the provided password hash is validated using salted bcrypt algorithms to establish session access.
This sequential resolution cascade ensures high fault tolerance while maintaining strict computational efficiency. It allows organizational executives, Branch Managers, and Field Recruits to log into the terminal seamlessly using whatever identifier they remember.
4. Workstation Binding & Hardware Fingerprint Security
To prevent staff login credentials from being used on unauthorized personal laptops, remote mobile devices, or home computers, I implemented custom hardware device fingerprinting. This client-side security protocol binds user sessions strictly to designated physical office terminals authorized by system administrators.
- Client Hash Generation: The frontend JavaScript engine computes a cryptographic hash combining browser environment properties, screen dimensions, WebGL rendering parameters, hardware concurrency counts, and canvas fingerprint tokens.
- Device Match: On successful credential verification, the calculated device hash is queried against approved master agency workstations in the database registry.
- Access Flagging: If
is approved == false, session issuance is immediately blocked, logging an "Unapproved Terminal" alert and rendering the hardware authorization request modal for Admin sign-off.
This client-side fingerprinting engine operates seamlessly without requiring external software installations or browser extensions, providing military-grade terminal access control inside standard WebKit and Chromium browsers.
5. Brute-Force Defense & Password Recovery Logic
To safeguard sensitive client and candidate operational data against automated dictionary attacks or credential stuffing, I constructed an automated threat mitigation pipeline directly inside the authentication service.
Account Lock & Recovery Workflow:
• Failed Password Attempts: Every unsuccessful login attempt increments the account counter failed login attempts. Reaching 5 consecutive failures automatically locks the target account and sets account locked until to 15 minutes in the future. The terminal UI displays an active locking timer and rejects incoming password attempts.
• Recovery Trigger: Requesting a password recovery dispatches a short-lived, cryptographically secure 6-digit dynamic PIN to the account's registered email address. Validating this dynamic PIN clears the locking status, resets failed login attempts to zero, and triggers the password update interface.
This automated protection loop guarantees high system resilience against automated intrusions while maintaining a self-service recovery pathway for legitimate operators without requiring server-level intervention.
6. Subscription Integration & Paywall State Engine
Monetization and licensing enforcement across active agency deployments are controlled through an automated subscription interceptor integrated with regional mobile money protocols and primary payment gateways.
Paywall Operational Steps:
- Expiration Check: Upon authentication, system middleware evaluates the agency's active subscription status against
subscription expires at. - Paywall Intercept: If the current timestamp exceeds subscription validity, the backend responds with a
402 Payment Requiredstatus code, restricting operational API endpoints and launching the subscription renewal interface. - Transaction Dispatch: When an Admin selects a renewal package (e.g., Monthly Pass at UGX 150,000) and enters a designated phone number, an automated USSD prompt is dispatched via PesaPal directly to the mobile phone (MTN MoMo or Airtel Money) for PIN verification.
- IPN Callback Handling: Upon transaction authorization, the Instant Payment Notification (IPN) webhook verifies the cryptographic transaction payload, updates
subscription expires at, logs the invoice receipt, and immediately unlocks agency access across all linked terminals.
7. Developer Operations & Troubleshooting Guide
To streamline developer maintenance, system updates, and operational support across remote deployments, consult these standard technical troubleshooting procedures:
Issue: Unapproved Device Error on Fresh Environment
Solution: Access the database management console or use a Master Admin terminal to set is approved = true in the device approvals table for the specific workstation fingerprint hash.
Issue: Payment cleared on gateway but Agency remains locked
Solution: Check the IPN listener endpoint logs to verify that incoming webhook notifications from PesaPal are accessible over HTTPS and that signature validation succeeded against the transaction order ID.
Issue: Account stuck in 15-minute lock state
Solution: Allow the account locked until expiration timestamp to elapse, or trigger an official password recovery dispatch to clear the counter and grant immediate access.
Comments
Post a Comment