📖 Afaqy Knowledge Base / Smart Taxi / Driver App / Authenticated Sessions
Overview
The Authenticated Sessions module manages driver access to the Smart Taxi ecosystem and ensures that only authorized drivers can operate registered vehicles.
Authentication establishes a secure operational session between the driver, vehicle, backend services, and regulatory systems.
A successful authentication process is required before any trip-related activity can be performed.
Purpose
The authentication process is designed to:
- Verify driver identity
- Establish a secure operational session
- Associate the driver with the assigned vehicle
- Enable trip lifecycle operations
- Support compliance and auditing requirements
- Synchronize operational data with backend services
Authentication acts as the entry point to all Smart Taxi operational workflows.
Authentication Workflow
A typical authentication workflow follows the sequence below:
- Driver launches the Driver App
- Driver enters authentication credentials
- Credentials are validated by the Smart Taxi backend
- Driver identity is verified
- Vehicle assignment is validated
- Operational session is created
- Driver gains access to application features
Upon successful authentication, the driver becomes operationally available.
Session Validation
After login, the system validates several operational requirements.
Driver Validation
The system verifies:
- Driver identity
- Driver account status
- Authorization to use the system
- Compliance eligibility
Drivers with inactive or restricted accounts may be prevented from accessing operational functions.
Vehicle Validation
The system verifies:
- Assigned vehicle
- Vehicle operational status
- Device registration status
- Connectivity availability
The driver must be associated with a valid operational vehicle before trip execution can begin.
Device Validation
The Smart Taxi ecosystem may validate connected devices, including:
- GPS/meter device
- Passenger tablet
- SIM connectivity
- Backend communication services
Device validation helps ensure accurate trip synchronization and reporting.
Active Session
Once authentication is completed successfully, an active session is established.
An active session allows the driver to:
- Start trips
- End trips
- Synchronize trip information
- Exchange fare information
- Participate in compliance workflows
- Access operational functionality
The session remains active until:
- The driver logs out
- The session expires
- Connectivity failures require re-authentication
- Administrative actions terminate access
Session Synchronization
During an active session, the Driver App continuously synchronizes data with the Smart Taxi platform.
Examples include:
- Driver status
- Vehicle status
- Trip activity
- Fare information
- GPS location
- Compliance events
This synchronization ensures operational visibility across the ecosystem.
Session States
Logged Out
The driver is not authenticated.
Available actions are limited to authentication-related functions.
Authenticated
The driver has successfully logged in and established an operational session.
The driver may access operational functions according to assigned permissions.
Session Expired
A session may expire due to:
- Extended inactivity
- Security policies
- Backend session timeout
The driver must authenticate again to continue operations.
Connectivity Interrupted
Occurs when communication with backend services becomes unavailable.
During this state:
- Synchronization may pause
- Operational updates may be delayed
- Some functionality may become unavailable
Normal operation resumes once connectivity is restored.
Security Considerations
Authenticated sessions are designed to:
- Protect driver accounts
- Prevent unauthorized access
- Maintain auditability
- Support regulatory compliance
- Preserve operational integrity
Drivers should never share authentication credentials with other users.
Operational Impact
Authentication directly affects:
- Driver availability
- Trip execution
- Compliance synchronization
- Reporting accuracy
- Vehicle assignment validation
Authentication failures may prevent drivers from participating in operational workflows.
Best Practices
- Verify internet connectivity before logging in
- Ensure assigned vehicle information is correct
- Use authorized credentials only
- Log out when operational activities are completed
- Report authentication issues to system administrators
- Avoid sharing credentials with other drivers
