Hi Team,
We are seeing inconsistent behavior with the ./lgfapi/v10/htmlrf/get_next_rwmobile_page API. In Postman, the API works fine, but through the VBCS endpoint the response only succeeds after multiple attempts.
Oracle has explained that this WMS API requires cookie handling, which VBCS and OIC do not automatically manage. Success depends on how the browser handles third‑party cookies. Knowledge Article KB872352 confirms that cookie management is required for WMS APIs, and I have already tried cookie handling in VBCS without success.
I also highlighted that Oracle WMS Cloud has a Mobile App built on VBCS (PWA). It would be useful to understand how Oracle implemented cookie handling in their Mobile App and whether similar guidance can be applied here. Any documentation on this would be appreciated.
For reference, I attempted dynamic authorization with cookie support as shown below:
javascript
console.log("Calling REST endpoint...");
// Example REST call with cookie support
const response = await Actions.callRest(context, {
endpoint: 'wms/lgfapi/v10/htmlrf/get_next_rwmobile_page',
headers: {
"Authorization": "Basic <encoded-credentials>",
"Content-Type": "application/json"
},
options: { withCredentials: true }, // ensures HttpOnly cookies are sent
body: {
htmlrfid: "sampleHtmlrfid",
clientid: "sampleClientId",
keyboard_input: "6",
action_keys: "TAB"
}
});
We need to capture the X-Oracle-HTMLRF-LBS-Route cookie value for subsequent API calls to enable navigation. Please let me know if anyone has successfully implemented this in VBCS.