Parivahan Vahan 4.0 Engine

Reverse-Engineered High-Performance JSF Automation & Session Orchestrator in Hono.js

Connecting...
Autonomous Complete Cycle
Single-Click: AI OCR Status Query → 1st App Number → Vehicle Auth → Document Transition → Owner Contact Extraction
End-to-End Pipeline
Preset Vehicles:
Vehicle Session Authenticator
Quick Samples:
Step 01 Standby
GET Homepage
Fetch initial DOM, extract encrypted JSF ViewState & dynamic form tokens
Waiting to trigger...
Step 02 Standby
POST Proceed Button
Ajax submit vehicle registration with terms accepted to render modal dialog
Waiting...
Step 03 Standby
POST Modal Proceed
Dynamically submit dialog button ID to trigger JSF server redirect
Waiting...
Step 04 Standby
GET Login Dashboard
Follow redirect, lock sticky session cookies & parse 33+ citizen services
Waiting...
Live Request Terminal & Diagnostic Logs
00:00:00 [SYSTEM] Ready. Enter vehicle registration number and click 'Execute 4-Step Auth Flow'.
Know Application Status (Autonomous AI OCR Solver) ResCRNN-CTC v3 Powered
Why the Earlier OpenBullet Request Failed & How It Works

In your original attempt, you posted to homepage.xhtml with hardcoded parameters and then immediately did an empty POST to login.xhtml. Here is why it failed and how our Hono.js engine resolves it:

  • Dynamic Component IDs: JSF dynamically assigns IDs like j_idt16, j_idt27, and j_idt243_input. Hardcoding them causes the JSF lifecycle to reject the submission. Our client parses the live DOM with Cheerio and extracts the active IDs dynamically.
  • Multi-Phase Modal Dialog: Submitting proccedHomeButtonId does not return a redirect; it returns an XML partial Ajax response that opens a PrimeFaces modal dialog (facelesslist). You must parse the button ID inside that dialog (e.g. j_idt528) and submit an Ajax POST for it.
  • Redirect is GET, Not Empty POST: The modal dialog returns <redirect url=".../login.xhtml?faces-redirect=true">. In JSF, a client redirect requires an HTTP GET with sticky session cookies, not an empty POST.
  • Sticky Load Balancer Cookies: Parivahan requires both JSESSIONID (scoped to /vahanservice) and SERVERID_175 (scoped to /). If the sticky cookie is omitted, requests route to different cluster nodes, destroying the session.
cURL Integration Command 
curl -X POST http://localhost:3000/api/vahan/auth/vehicle \
  -H "Content-Type: application/json" \
  -d '{"regNo": "ML05M4483"}'