After Upgrade facing issue with 'Consent Popup' & 'custodian' org

[komalm]

Hello @reshmi-nair @AmiableAnil @vinukumar-vs,

Sunbird Version - 4.10.0

Background -
We have upgraded the sunbird version from 4.4.1 to 4.10.0
Before upgrade we were not facing the following issue.

Issue Details -

1. After successfully logging in with a freshly registered user (generated from the backend, specifically Postman), the user is unable to accept the consent.

After checking this box, the continue button is still disabled.becase in the code the condition is failed is 'updateConsent'

Note above issue not only for the 'custodianOrgId'.

More Details

Request URL

Request URL: https://host/learner/user/v1/consent/read
Request Method: POST
Status Code: 404 Not Found

Payload -

{
    "consent": {
        "filters": {
            "userId": "58bc46d2-f612-43bf-89e8-7e2e3e9fc60f",
            "consumerId": "0138778647572152323",
            "objectId": "0138778647572152323" 
        }
    }
}

Response

{
    "resmsgid": "2c2f338d165f103bce9a429654fdc734",
    "msgid": "2c2f338d165f103bce9a429654fdc734",
    "err": "USER_CONSENT_NOT_FOUND",
    "status": "USER_CONSENT_NOT_FOUND",
    "errmsg": "Requested user consent resource not found" 
} 

2. The issue we're having with custodian org is that when I register a user with custodian org and login with that user, I receive a discovery window with no options in the select field.

3. The issue we're having with custodian org is that when we are enroll to the course with the custodian org user.

Request URL

Request URL: https://host/learner/user/v1/consent/read
Request Method: POST
Status Code: 404 Not Found
Remote Address: 20.244.62.154:443
Referrer Policy: strict-origin-when-cross-origin

Payload -

{
    "consent": {
        "filters": {
            "userId": "106abf62-82fa-4c62-8300-baf3b36ccb4b",
            "consumerId": "0130152125009674241",
            "objectId": "do_113848746566967296117"
        }
    }
}

Response -

response
{
    "id": "api.user.consent.read",
    "ver": "v1",
    "ts": "2023-09-11 05:31:32:046+0000",
    "params": {
        "resmsgid": "e44c976cf910e82c52e1d866d5dece9a",
        "msgid": "e44c976cf910e82c52e1d866d5dece9a",
        "err": "USER_CONSENT_NOT_FOUND",
        "status": "USER_CONSENT_NOT_FOUND",
        "errmsg": "Requested user consent resource not found"
    },
    "responseCode": "RESOURCE_NOT_FOUND",
    "result": {}
}

Update Consent Request URL -

Request URL: https://host/learner/user/v1/consent/update
Request Method: POST
Status Code: 400 Bad Request
Remote Address: 20.244.62.154:443
Referrer Policy: strict-origin-when-cross-origin

Response -

{
    "id": "api.user.consent.update",
    "ver": "v1",
    "ts": "2023-09-11 05:31:36:367+0000",
    "params": {
        "resmsgid": "531b1f2b20429cc98d7195bf2d68a28d",
        "msgid": "531b1f2b20429cc98d7195bf2d68a28d",
        "err": "UOS_UCNSNTUPD0019",
        "status": "FAILED",
        "errmsg": "Please provide valid organisationid."
    },
    "responseCode": "CLIENT_ERROR",
    "result": {}
}

cc @Renuka-S, @vinod303, @coolbung, @Nithin-ns24 @sravani-64, @gandham-santhosh, @paritshivani

[mohitga]

@AmiableAnil can you look into this issue?

[AmiableAnil]

@komalm
What is the request body is passing in consent update API? In the response it is saying that "errmsg": "Please provide valid organisationid."

[komalm]

@AmiableAnil For Update API payload is the

{
    "request": {
        "consent": {
            "status": "ACTIVE",
            "userId": "106abf62-82fa-4c62-8300-baf3b36ccb4b",
            "consumerId": "0130152125009674241",
            "objectId": "do_113848746566967296117",
            "objectType": "Collection"
        }
    }
}

[komalm]

We have one question,

Can we update/change the Custodian Org ID?

Because the majority of the content and users in our case are created in the Custodian Org ID

cc @@sravani-64

[AmiableAnil]

@komalm Please refer this code
If the consumerId is equals to custodianOrgId than this error is throwing.

[paritshivani]

@AmiableAnil ,
As all users are from current custodianOrg, both consumerId and custodianOrgId are same. but we cant change consumerId of users. Can we change custodianOrgId to any other orgnzation anyhow?

For more detailed discussion can we have a quick call today? this issue is critical and shows topper for us. we need to fix it in high priority.

cc @Renuka-S, @vinod303, @coolbung, @Nithin-ns2, @komalm , @sravani-64

[Krishnaj20]

@AmiableAnil @rajeevsathish - this is a blocker for Tekdi team. Please look into this today. If needed, pls get into a call.

@mohitga

[AmiableAnil]

@Krishnaj20 Scheduled a call at 2:30PM today.

[AmiableAnil]

@komalm @paritshivani Please update the call summary here.

[Krishnaj20]

thanks @AmiableAnil for taking out time to set up a call.

@Renuka-S @vinod303, @coolbung, @Nithin-ns2, @komalm , @sravani-64 - as requested by @AmiableAnil it is a good practice to summarize async conversations so that community and wider audience can benefit from this. Request that the call summary be posted here. Thanks

[Renuka-S]

@AmiableAnil @rajeevsatish Thank you so much for the call yesterday. As discussed over call we updated configurations and testing is in progress for impact. Will add the detailed updates and result in couple of days here. cc: @Krishnaj20

[Jayaprakash8887]

@Renuka-S Kindly update. Also, please mark the ticket as answered if there are no further concerns.

[paritshivani]

@AmiableAnil , @rajeevsatish, @Krishnaj20 ,
Tank you for your support.
Above issues got resolved after following steps mentioned bellow

1. For consent issue: we have this issue wile manual creation of user on postman. We need to compaire steps wit portal registration form
2. For discovery popup: We have redeployed the knowledge MW service and also added framework array to organisation
3. Custodian org issues, we changed thecustodian org id and custodian org channel wit system setting api
   API url: 'baseurl/api/data/v1/system/settings/set'
   Request body for custodian org Id: {
   "request": {
   "id": "custodianOrgId",
   "field": "custodianOrgId",
   "value": "{{organisationId}}"
   }
   }
   Request body for custodian org cannel: {
   "request": {
   "id": "custodianOrgChannel",
   "field": "custodianOrgChannel",
   "value": "nulp-mainorg"
   }
   }

[AmiableAnil]

@paritshivani Thanks for summarizing it. @komalm Please mark this thread as Answered.