Post installation and issue with main home landing page

[simhead]

Hi,

This is what I've done so far:

• ported code to work with OCI using 'oci-integration' branch
• infra provision - done
• helm deployment by install.sh - done
• First landing page as Guest - seems to be fine

More deep-dive with browser's network tool, I see some errors:

1. 403 for PATCH https:///learner/user/v3/update
   With payload: {"params":{},"request":{"framework":{"board":["CBSE"],"medium":["English"],"gradeLevel":["Class 1"],"subject":[],"id":"NCF"}}}
   Response: {"message":"You cannot consume this service"}
2. 404 for POST https:///api/data/v1/form/read
   With payload: {"request":{"type":"profileConfig_v2","action":"get","subType":"ka","rootOrgId":"0143364283732705282","framework":"NCF"}}
   Response:
   { "id": "api.form.read", "params": { "resmsgid": "9582c3a3-8d03-4ead-9ec5-ca4291d1a80b", "msgid": "5275a543-7bdd-45df-b612-74fd8dac3fea", "status": "failed", "err": "ERR_READ_FORM_DATA", "errmsg": { "message": "data.toJSON is not a function", "stack": "TypeError: data.toJSON is not a function\n at /home/sunbird/app_dist/node_modules/@project-sunbird/form-service/server.js:163:29\n at tryCatcher (/home/sunbird/app_dist/node_modules/bluebird/js/release/util.js:16:23)\n at Promise._settlePromiseFromHandler (/home/sunbird/app_dist/node_modules/bluebird/js/release/promise.js:547:31)\n at Promise._settlePromise (/home/sunbird/app_dist/node_modules/bluebird/js/release/promise.js:604:18)\n at Promise._settlePromise0 (/home/sunbird/app_dist/node_modules/bluebird/js/release/promise.js:649:10)\n at Promise._settlePromises (/home/sunbird/app_dist/node_modules/bluebird/js/release/promise.js:729:18)\n at _drainQueueStep (/home/sunbird/app_dist/node_modules/bluebird/js/release/async.js:93:12)\n at _drainQueue (/home/sunbird/app_dist/node_modules/bluebird/js/release/async.js:86:9)\n at Async._drainQueues (/home/sunbird/app_dist/node_modules/bluebird/js/release/async.js:102:5)\n at Immediate.Async.drainQueues [as _onImmediate] (/home/sunbird/app_dist/node_modules/bluebird/js/release/async.js:15:14)\n at processImmediate (node:internal/timers:466:21)" } }, "responseCode": "SERVER_ERROR", "result": {}, "ts": "2025-08-14T23:21:11.039Z", "ver": "1.0" }

I can see other 'read' calls are giving 200 OK, e.g. with payloads like:

1. {"request":{"type":"onboardingPopupVisibility","action":"onboarding","subType":"global","rootOrgId":"0143364283732705282","component":"portal","framework":"*"}}
2. {"request":{"type":"newUserOnboarding","action":"onboarding","subType":"global","rootOrgId":"0143364283732705282","component":"portal","framework":"*"}}
3. {"request":{"type":"contentcategory","action":"menubar","subType":"global","rootOrgId":"0143364283732705282","framework":"*"}}
4. {"request":{"type":"content","action":"search","subType":"resourcebundle","rootOrgId":"0143364223382650880","framework":"*"}}
5. {"request":{"type":"user","action":"update","subType":"framework","rootOrgId":"0143364223382650880","framework":"NCF"}}

Anyone can shed some light?

[JeraldJF]

@simhead

1. For the first api failure 403 for PATCH https:///learner/user/v3/update, It says there is no necessary permission to consume the service, please check the Authorization token. Use a valid authorization token and try consuming the service.
2. For the second api failure, it says that the form with payload:
   {"request":{"type":"profileConfig_v2","action":"get","subType":"ka","rootOrgId":"0143364283732705282","framework":"NCF"}}
   is not created. Create it and the issue will be solved. If you face any other issues, please report it here.

[simhead]

@JeraldJF
I have ran all post api postman collection as below:

So the question is where this "rootOrgId":"0143364283732705282" came from and why it is complaining?
i.e. https://raw.githubusercontent.com/project-sunbird/sunbird-ed-installer/refs/heads/main/postman-collection/collectionrelease700.json

Hope to hear from you soon.

[JeraldJF]

@simhead The rootOrgId is generated when the postman collection is executed. When the default organisation is created, the rootOrgId is generated which will be used throughout form creation.
Are the above listed issues are fixed?

[simhead]

Closing for now as this was info-needed ticket