VW Hub Source
VW Hub (www.vwhub.com) is the Volkswagen of America dealer OMS. Its Liferay site is named
OMD (group omd-usa-vw-dealer). It runs on the same VWoA ISAM / WebSEAL / Liferay stack as
AccessAudi. Every fact below comes from one capture. It
recorded a read-only dealer session of about five minutes. The dealer visited the Vehicle
Tracking, Trade Management and Report a Sale pages. No order was configured or submitted,
and no allocation page was opened.
Placeholders: <UPPER_SNAKE> stands for a redacted captured value, and a lowercase <slot> is
a template parameter. Product codes (carline, sale model, option, color) are catalog values
and appear as captured.
Hosts and authentication
Archetype
liferay_portlet: Liferay 7.x Angular portlets (zone.js, PrimeNG, short portlet ids such as
p55_v4, p68, p76) behind an IBM WebSEAL reverse proxy. Every data call is a Liferay
portlet resource request to one URL:
/omdjct/c/portal/layout?p_l_id=<layoutId>&p_p_id=<portletId>&p_p_lifecycle=2
&p_p_cacheability=cacheLevelPage&p_p_resource_id=/omd/voa/dlr/<section>/<cmd>/view
p_p_resource_ididentifies the call. It is a path-style MVC resource command. AccessAudi uses verb names instead.p_l_idis the page layout id and differs per page. Scrape it from the page that hosts the portlet instead of hardcoding it.- GET requests send their parameters in the query string, namespaced by portlet
(
_p55_v4_brand,_p68_vehicleType). - POST requests are
application/x-www-form-urlencodedwith portlet-namespaced fields (_p76_startDate,_p76_page_dealerCode). The trade search sends a URL-encoded JSON object in one field,_p76_searchRequestParams. - Responses are bare JSON arrays or objects, with no
{data, status}envelope.
A second, smaller family is Liferay JAX-RS under /omdjct/o/products/.
These calls return no business data: POST /omdjct/rb_<guid> (Dynatrace RUM beacons),
/omdjct/o/js_resolve_modules (Liferay AMD loader), tile.openstreetmap.org (route map
tiles).
Hosts
| Host | Role |
|---|---|
www.vwhub.com | The OMS and the only authenticated host. All data calls go to the /omdjct junction. |
media.volkswagen.com | Public vehicle-image CDN. /o/products/image returns URLs on this host. |
| WebSEAL junction | Purpose | Needed for replay |
|---|---|---|
/omdjct | Liferay application | Yes |
/extsamljct | ISAM FIM SAML 2.0 SP (/extsamljct/sps/extsamljct/saml20) | No |
/sps | Security provider service | No |
/mga | ISAM management gateway | No |
The junction names differ from AccessAudi's (/lr, /audijct). Audi junction strings do
not work on VW Hub.
Auth flow
Authentication uses ISAM WebSEAL with ISAM FIM SAML 2.0 SP federation on /extsamljct.
Liferay keeps a second SAML SP session (SAML_SP_SESSION_KEY on /omdjct). The capture starts
mid-session, so no login exchange was recorded.
The IdP host is not confirmed. Two facts point to a VW Group internal host. The Login
cookie names a .cpn.vwg (VW Group internal) domain. The AccessAudi IdP issuer is
https://lr.vwoa.na.vwg.
Re-authentication without the dealer is not possible. Login is interactive SAML through the VWoA dealer IdP, and no refresh token or long-lived credential appears. Cookie Monster captures the session from the dealer's browser. A raw asset skips while no valid session exists.
Minimum cookie set
| Cookie | Role | Rotates |
|---|---|---|
PD-H-SESSION-ID | WebSEAL session handle (1_4_<n>_<...>); the session cookie | No |
EncryptCookie | WebSEAL encrypted session payload (! then base64) | No |
AMWEBJCT!%2Fomdjct!JSESSIONID | Liferay application-server session, mangled by WebSEAL for /omdjct | No |
This set is inferred and not proven on VW Hub. It comes from drop tests on AccessAudi. A drop test replays a request with one cookie removed. The capture cannot show which cookies the server requires. Every request that sent cookies sent the same 20 cookies. No response set a cookie.
EncryptCookiewas never drop-tested on either OMS. It is the cookie most likely to prove optional.- On AccessAudi, the plain name
JSESSIONIDworks in place of the mangled name. - The
%2Fand/spellings of the junction segment are equivalent.
Cookies that are not required, by name pattern:
| Pattern | Why it is not required |
|---|---|
^AMWEBJCT!(%2F|/)(extsamljct|mga|sps)! | SAML handshake and admin junctions, not on the data path |
AMWEBJCT!%2Fomdjct!SAML_SP_SESSION_KEY | Liferay SAML SP tracking; JSESSIONID holds the Liferay session. Not drop-tested. |
AMWEBJCT!%2Fomdjct!COOKIE_SUPPORT, AMWEBJCT!%2Fomdjct!GUEST_LANGUAGE_ID, Login | Constant page settings |
^PD_STATEFUL_ | WebSEAL junction routing hints whose names embed junction GUIDs |
^LFR_SESSION_STATE_ | Client-side last-activity timestamp; the name embeds the Liferay user id |
^dt, ^rx | Dynatrace RUM telemetry, changed by client JS on almost every request |
Allowlist the three required cookies and drop everything else. A fixed denylist breaks when junction GUIDs or user ids change.
SessionSpec
| Field | Value |
|---|---|
domain | www.vwhub.com |
session_cookie | PD-H-SESSION-ID |
required_raw_cookies | EncryptCookie, AMWEBJCT!%2Fomdjct!JSESSIONID |
The Audi UserCookiesResource in projects/ai_audi/src/ai_audi/definitions.py uses the
same three-cookie pattern.
CSRF
The CSRF token is Liferay.authToken, an 8-character alphanumeric JS global
(Liferay.authToken = '<CSRF_TOKEN>';) in every page's HTML, for example
GET /omdjct/group/omd-usa-vw-dealer/vehicle-tracking. Scrape it once per session; it did
not rotate. It is sent as the x-csrf-token header on every XHR to /omdjct/c/portal/layout
and /omdjct/o/products/*, GET requests included. No p_auth query parameter appears.
Whether the server enforces the header on GET requests is untested, so always send it.
Session expiry
No session expired in the capture: every response was 200 or 304. The rule below is
inferred from the Liferay session config in each page (sessionLength: 7200,
autoExtend: false, redirectOnExpire: true, redirectUrl /omdjct/web/guest).
An expired session is expected to return either a 3xx to /omdjct/web/guest, or a 200
whose body is HTML (the WebSEAL pkmslogin form, or the SAML auto-POST through
/extsamljct/sps/.../saml20). To detect it:
- Send requests with redirects disabled.
- Treat any 3xx as expired.
- Treat any body that does not parse as JSON as expired.
- Match the markers
pkmslogin,saml20andSAMLRequest. The AccessAudi markersaml20/logindoes not match VW Hub's federation path.
An empty array is a healthy response. Several endpoints returned [] in a live session;
they are listed under Extraction traps.
The idle timeout is not measured. Liferay's sessionLength is 7200 s, but WebSEAL's
inactivity and lifetime timeouts are a separate layer. No /c/portal/extend_session call
appears.
Bot protection and dealer context
The capture shows no bot protection: it has no Akamai or Cloudflare cookies. Dynatrace RUM is telemetry only.
dealerCode (6 digits) is sent per request in the query or POST body
(_p55_v4_dealerCode, _p76_page_dealerCode). The header dealer picker
(/omd/voa/dealer_search/favorites/view) returned null for a single-dealer user. No
dealer-context switch was observed.
Data domains
All data is bare JSON. No PDF, CSV or XLS export was captured. Every captured call is a
read. Every captured POST is a search or history query whose resource id ends in /view.
The full endpoint list is in vwhub-analysis.json.
| Domain | Coverage | Endpoint families |
|---|---|---|
| inventory_pipeline | Exposed | vehicle_tracking/*, sales_reporting/vehicles (on-lot stock) |
| sales_history | Exposed (dealer trades only); retail sales not captured | trade_management/trade_history* |
| cross_dealer_market | Exposed | trade_management/trade_search_*, trade_activity, administration/partners, trade_contact_info |
| product_configurator | Exposed (catalog only, no rules or pricing) | trade_management/search_criteria_*, /o/products/* |
| ordering_rules_timing | Exposed (order-cycle history only) | alerts |
| allocation_volume_schedule | Not captured | Allocation pages are in the navigation, never opened |
| deferred_allocation_pools | Not captured | MBO pool pages are in the navigation, never opened |
inventory_pipeline
GET vehicle_tracking/vehicles/view(brand,dealerCode): one row per vehicle with(commNum, commYear), VIN, carline and sale model, colors,factoryOptions,marketDeliveryOptions,msrp,orderType,orderStatus,vehicleMilestoneKey,eta, and a milestone timestamp series fromorderCreatedthroughdealerDelivered.GET vehicle_tracking/route/view(percommNumandcommYear): logistics legs FACTORY → PORT → DEALER with latitude, longitude and location type.watchlist,favorites,vehicle_holds: the dealer's saved vehicle lists; all returned[].POST trade_management/pipeline_search_vehicles_by_criteria/view: matches the dealer's own production pipeline against the trade-search criteria ("My Pipeline"); returned[].
The tracking list is not complete on-lot stock. It held far fewer delivered units than
sales_reporting/vehicles held delivered-unsold (orderStatus 50) units. Read both and
merge on (commNum, commYear).
sales_history
GET sales_reporting/vehicles/view(vehicleType=NEW): the Report-a-Sale (RDR) worklist. Most rows areorderStatus 50with a nullvehicleSaleDate(delivered, unsold); the rest areorderStatus 60with a sale date andhasSavedReport=true.vwhub-analysis.jsonclassifies it as sales_history, after the OMS's name for it. Most of its rows are on-lot unsold stock, so it is also the best on-lot inventory source.GET sales_reporting/reporting_data/view:{saleReportDate, reportSaleEnabled}.GET sales_reporting/dealer-personnel/view: dealer staff for the RDR salesperson picklist. Every record is personal data; do not persist it.POST trade_management/trade_history/view(requestType=BOTH,startDateandendDateasYYYY-MM, 12-month window): dealer-to-dealer trades withrequestTypeINCOMING / OUTGOING,tradeStatus,tradeDate.POST trade_management/trade_history/chart/view: monthly incoming and outgoing trade totals by carline, trim, sale model and exterior-color category.
Retail sales history was not captured. Page JS references sale-report/submitted/view,
sale-report/saved/view and sold-order-details/view, and the navigation lists REPORTED
SALES HISTORY and SOLD ORDERS.
cross_dealer_market
Trade Management is dealer-to-dealer trading of units, not allocation trading.
POST trade_management/trade_search_vehicles_by_criteria/view: the form field_p76_searchRequestParamsholds URL-encoded JSON{modelYears, carlineCodes, saleModelCodes, exteriorColorCodes, interiorColorCodes, includeFactoryOptionCodes, stateCodes, pageSize, pageNum, orderByColumns}. Returns paged{tradeSearchResults[], totalElements}over peer-dealer pipeline and stock:owningDealerCode,proximity(miles),region/area/state,tradeStatus,eta, milestone,msrp,assignedPort. Filtering bystateCodeswithpageSize: 500could read cross-dealer inventory one state at a time. This use is untested at volume.GET trade_management/trade_activity/view(requestTypeBOTH / OUTGOING): open trade requests, with fields includingrequestAge,stockAge,productionWeek, and requestor contact data.GET trade_management/administration/partners/view:partneredByMe/partneredByThemdealer lists with region and area.GET trade_management/trade_contact_info/view(lookupDealerCode): a peer dealer's contacts and free-text add-on pricing instructions.GET trade_management/trade_search_favorites/view: saved searches; returned[].
The dealer's own data is keyed by dealerCode. The trade search fans out over
modelYears and carlineCodes from search_criteria_carlines, or over stateCodes. To
page through results, increment pageNum until totalElements rows are read.
product_configurator
The trade-search criteria lookups also serve as the model-year catalog (MY2022 to MY2027 in the capture).
GET search_criteria_carlines/view:(modelYear, carlineCode, carlineFamilyDesc).GET search_criteria_salemodels/view(carlineCodes,modelYears):salesModelCode, description,trimShort,fuelType,engine,transmission,drivetrain.GET /omd/dlr/trade_management/search_criteria_colors/view: exterior and interior pairs, each withavailableModels[{modelYear, saleModelCode}].GET /omd/dlr/trade_management/search_criteria_sale_options/view: option codes withportInstalledIndandavailableModels[].GET /omdjct/o/products/option/description/{modelYear}?optionCode=<csv>: code to description map.GET /omdjct/o/products/image?commNum=&commYear=&vin=:{vehicleImageUrl}onmedia.volkswagen.com.
availableModels gives color and option validity per sale model. There are no
option-compatibility rules and no pricing catalog. Pricing is published as "Price and Order
Guide" PDFs under /omdjct/documents/..., linked from alerts. MSRP appears only on vehicle
rows.
ordering_rules_timing
GET /omd/voa/alerts/view returns every notification back to 2020 as
{notificationId, title, description, category, displayDate, link}. Most are order-cycle
opened and closed notices. They give the history of the order-cycle calendar and do not
list future cycles:
MBO cycle opens around day 2-4 of each month, stays open 1-4 days
FSO cycle opens mid-month for about 1 day
title "<FSO|MBO> <MON> <YYYY>-<letter> Order Cycle Opened!" / "...Closed!"
links /mbo-suggested-orders, /factory-suggested-orders
Parse the calendar from alert titles and displayDate. The navigation lists an ORDER CYCLE
SCHEDULING page, never opened.
Dealers order only while an FSO (factory-suggested) or MBO cycle is open, so a capture of
the submit or accept requests must be made inside an open cycle. The navigation lists these
ordering pages, and none was opened: factory-suggested-orders,
mbo-suggested-orders, allocation-summary, allocation-summary-fo, allocation-history,
mbo-pool-analysis, fso-production-analysis, pipeline-management, options-management.
The i18n bundle contains ACCEPTED, MBO ALLOCATION and ORDER CYCLE PREPARATION, which suggests
a suggested-order accept or modify flow; this is unconfirmed.
Write commands seen in page JS only
None were sent, so no request format is known. Do not build requests from the names alone.
trade_activity/update is a dealer-trade accept or decline, not a factory order.
trade_request/submit, trade_activity/update
administration/partners add|remove, administration/trade_rule add_or_update|remove
contact update|delete
watchlist / favorites add|remove
sale-report save|submit|delete
courtesy_vehicle_program enroll|deactivate
Extraction traps
- The row fields of
watchlist,favorites,vehicle_holds,trade_search_favorites,pipeline_search_vehicles_by_criteriaanddisplay_boardare unknown; do not build schemas for them yet. - The image endpoint's bodies are missing from the capture because a web worker issued the
requests. The worker requests also show no
Cookieheader; the endpoint is still authenticated. search_criteria_colorsandsearch_criteria_sale_optionsuse the prefix/omd/dlr/; every other command uses/omd/voa/dlr/. Normalizing the prefix produces a command the server does not know.
Personal data in responses
| Endpoint | Fields |
|---|---|
sales_reporting/dealer-personnel | staff names, phones, emails, address, MDM / UDE ids |
sales_reporting/vehicles | customerName on sold rows |
trade_management/trade_activity | requestorContactName / Email / Phone, actionedByContactName |
trade_management/trade_history | requestorContactName, actionedByContactName |
trade_management/trade_contact_info | primaryContact, secondaryContact |
trade_management/administration/partners | addByUser (OMS username) |
Identifiers
Hierarchy
Brand brand=VLK in requests (VW in trade_contact_info)
Model year 4-digit modelYear
└── Carline 4-char carlineCode (TIGN, AT2G, ID41) + carlineFamilyDesc ("ATLAS")
└── Sale model 6-char saleModelCode (RM14QJ, DJ14WJ); trim implied
├── Colors extColorCode (4) / intColorCode (2)
└── Options 3-char codes: factoryOptions + marketDeliveryOptions (port-installed)
Vehicle (order) (commNum, commYear), VIN once assigned
One carline family spans several carline codes (ATLAS is AT1F, AT2G and ATLP).
Color and option validity is defined per (modelYear, saleModelCode), not per carline.
Keys
| Identifier | Format | Notes |
|---|---|---|
commNum + commYear | 6 alphanumeric (AA9999, 9A9999, 999999, A99999) + 4-digit year | The vehicle and order key. The key is the pair, never commNum alone. |
| VIN | 17 chars | null until assigned (rows at orderStatus 15 / VEH_MILESTONE_ORDERED have none). Never use VIN as the key of a table of pipeline vehicles. |
dealerCode | 6 digits | Appears in responses as billToDealerCode, shipToDealerCode, owningDealerCode, requestingDealerCode, dealerPartnerCode, dealerNumber |
brand | VLK / VW | Aliases on different endpoints |
carlineCode | 4 chars | Group by carlineFamilyDesc, not by a code prefix |
saleModelCode | 6 chars | Reused across model years; what each character encodes is not confirmed, so do not parse it |
trimShort | free text (SEL AWD) | No trim code exists; trim is implied by saleModelCode |
| option code | 3 chars (P04, VPG, 0P8) | Identity is (modelYear, optionCode) |
extColorCode / intColorCode | 4 chars (usually a 2-char code twice: 0R0R) / 2 chars (PX) | |
orderStatus | integer: 5, 10, 15, 20, 30, 50, 60 | 50 delivered and unsold, 60 sold with a saved sale report; the other labels are not in the capture |
orderSubStatus | <status>-<n> (15-1) or null | |
vehicleMilestoneKey | VEH_MILESTONE_ORDERED, _PROD_COMPLETE, _FACTORY_OUTBOUND, _PORT_ARRIVED, _RTC, _DELIVERED | |
orderType | string '1' / '2' | Meanings unlabeled. AccessAudi's 1 = SOLD / 2 = SHIP mapping is not confirmed for VW. |
productionWeek | WW-YYYY | |
| order cycle | <FSO|MBO> <MON> <YYYY>-<letter> | Seen only in alert titles; the field name is unknown |
vtrIdent, dtpIdent, dtcIdent, invIdent, notificationId | integers | Trade request, trade partner, trade contact, inventory and alert ids |
region, area, state | 3 letters, 2 chars, USPS code | One payload pads area with a trailing space; trim it |
currentLocationIdent (7 digits) is not a dealer code, and currentLocationCode (6200)
is a factory location.
The canonical model key is (modelYear, saleModelCode). Add carlineCode when grouping
by carline. Every search_criteria_salemodels row is unique on this pair.
Pitfalls
commYearis notmodelYear; they differ on most records. A join on(commNum, modelYear)silently mismatches vehicles.search_criteria_salemodelsspells the modelsalesModelCode; every vehicle endpoint spells itsaleModelCode.sales_reporting/vehiclesspells the yearcommNumYearand returns a string; tracking and trade use the numbercommYear. Normalize to one integer column.sales_reporting/vehiclesspells the colorsexteriorColorCode/interiorColorCode; the other endpoints useextColorCode/intColorCode.orderTypeis a string. Typing it as an integer loses alphabetic codes if they appear, as they do on AccessAudi.
| Identifier | vehicle_tracking/vehicles | sales_reporting/vehicles | trade search / activity | search_criteria_* | /o/products/* |
|---|---|---|---|---|---|
commNum | ✓ | ✓ | ✓ | ✗ | ✓ (image) |
commYear | ✓ | ✓ (commNumYear, string) | ✓ | ✗ | ✓ (image) |
| VIN | ✓ (null until assigned) | ✓ | ✓ | ✗ | ✓ (image, optional) |
modelYear | ✓ | ✓ | ✓ | ✓ | ✓ (option description path) |
carlineCode | ✓ | ✓ | ✓ | ✓ | ✗ |
saleModelCode | ✓ | ✓ | ✓ | ✓ (salesModelCode) | ✗ |
trimShort | ✓ | ✗ | ✓ (trimShortDesc, trade activity only) | ✓ (salemodels) | ✗ |
| color codes | ✓ | ✓ (exteriorColorCode / interiorColorCode) | ✓ | ✓ (colors) | ✗ |
| option codes | ✓ (two lists) | ✓ | ✓ (filter) | ✓ (sale_options) | ✓ (option description) |
| dealer code | ✓ (billToDealerCode, shipToDealerCode) | ✗ (request parameter only) | ✓ (owningDealerCode, requestingDealerCode) | ✗ | ✗ |
orderStatus | ✓ | ✓ | ✓ | ✗ | ✗ |