in ipad.h, in struct ipa_config, the user may specify a callback function (prfle_inst_consent_cb), so that the IPAd can request for user consent during a profile intallation. When the callback function is not provided, the IPAd will assume that the answer to the user consent is always "yes".
However, in the IoT context, this feature does not make too much sense and in SGP.32, v. 1.2 also excludes this part by referring to 3.1.3.3 of SGP.22, which does not mention to query for user consent at all. This is done in SGP.22 section 3.1.3.2, which is not referenced by SGP.32. Instead SGP.32 describes the steps in section 3.2.3.2 directly. From the ESipa and ES10x perspective those steps are almost identical to the ones in SGP.22 section 3.1.3.2.
So there are two things to do here:
- remove the prfle_inst_consent_cb and the related code entirely
- revisit proc_prfle_dwnld.c and rework the spec references, so that they match SGP.32 properly.
in ipad.h, in struct ipa_config, the user may specify a callback function (prfle_inst_consent_cb), so that the IPAd can request for user consent during a profile intallation. When the callback function is not provided, the IPAd will assume that the answer to the user consent is always "yes".
However, in the IoT context, this feature does not make too much sense and in SGP.32, v. 1.2 also excludes this part by referring to 3.1.3.3 of SGP.22, which does not mention to query for user consent at all. This is done in SGP.22 section 3.1.3.2, which is not referenced by SGP.32. Instead SGP.32 describes the steps in section 3.2.3.2 directly. From the ESipa and ES10x perspective those steps are almost identical to the ones in SGP.22 section 3.1.3.2.
So there are two things to do here: