Started by an SCM changeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.org000022465224651.08511851103097685108510317abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/master7abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/master7abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/masterhttps://gerrit.osmocom.org/onomondo-eimhttps://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/31/artifacthttps://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/changeshttps://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/31/https://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/31/testReportfalse#312246530439master-onomondo-eim #3131falsefalse31168310SUCCESS1784030108892https://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/31/src/esipa_asn1_handler.erl1b43403ece8ccd4e80eaaca59dc364ec6910c89e1784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orges9p_client: convert InitiateAuthenticationOkEsipa to match SGP.32 V.1.2 In SGP.32 V.1.0.1, InitiateAuthenticationOkEsipa is almost identical to SGP.22 InitiateAuthenticationOkEs9. However, in SGP.32 V.1.2, the member euiccCiPKIdToBeUsed is renamed to euiccCiPKIdentifierToBeUsed. This means it is no longer possible to pass InitiateAuthenticationOkEsipa as InitiateAuthenticationOkEs9 to ES9+ directly. Instead we have to re-build the the InitiateAuthenticationOkEs9 from the contents of InitiateAuthenticationOkEsipa. Change-Id: I44c60a2f0d1129093ea67908d2eed167643a4a87 Related: SYS#8100 2026-07-14 11:53:08 +00001b43403ece8ccd4e80eaaca59dc364ec6910c89ees9p_client: convert InitiateAuthenticationOkEsipa to match SGP.32 V.1.2editsrc/esipa_asn1_handler.erlsrc/esipa_asn1_handler.erl63a9aa184a52e66571ae482e7abd31e1e695d3b91784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgesipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6 Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce Related: SYS#8100 2026-07-14 11:53:08 +000063a9aa184a52e66571ae482e7abd31e1e695d3b9esipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6editsrc/esipa_asn1_handler.erlcontrib/tryme_configureImmediateEnable.shcontrib/tryme_configureAutoEnable.shsrc/esipa_rest_utils.erlcontrib/rest_api_response_schema.jsoncontrib/rest_api_resource_schema.json8a1256049cd8ba69bce7f41fc317889a339c216f1784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgesipa_rest_utils: re-align to SGP.32 Section 2.11.2 Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308 Related: SYS#8100 2026-07-14 11:53:08 +00008a1256049cd8ba69bce7f41fc317889a339c216fesipa_rest_utils: re-align to SGP.32 Section 2.11.2editcontrib/rest_api_resource_schema.jsonaddcontrib/tryme_configureImmediateEnable.sheditsrc/esipa_rest_utils.erleditcontrib/rest_api_response_schema.jsondeletecontrib/tryme_configureAutoEnable.shcontrib/rest_api_response_schema.jsoncontrib/rest_api_resource_schema.json7abf280e10af25a82cccb9abc7e8b19240a878511784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgrest_api: move "required" member to the correct level In some locations in the JSON schema files we find the "required" member on the same level as the members of "properties" (likewise "items"). This is incorrect, the "required" member should always be on the same level as the "properties" or "items" member. (At the moment the JSON schema files serve only documentation purposes, they are not used to do any actual validation yet.) Change-Id: I07d51d0e809a718144bd51a6540ab51187bb4daa Related: SYS#8100 2026-07-14 11:53:08 +00007abf280e10af25a82cccb9abc7e8b19240a87851rest_api: move "required" member to the correct leveleditcontrib/rest_api_resource_schema.jsoneditcontrib/rest_api_response_schema.jsongithttps://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforgeBRANCHmasterEMAIL_NOTIFICATIONSjenkins-notifications@lists.osmocom.org laforge@gnumonks.orgStarted by upstream project "master-onomondo-eim" build number 3131master-onomondo-eimjob/master-onomondo-eim/000021767217671.0000317abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/master7abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/master7abf280e10af25a82cccb9abc7e8b19240a878517abf280e10af25a82cccb9abc7e8b19240a87851origin/masterhttps://gerrit.osmocom.org/onomondo-eimfalse#312176729516master-onomondo-eim » a1=default,a2=default,a3=default,a4=default,osmocom-master #3131falsefalse31168311SUCCESS1784030108892https://jenkins.osmocom.org/jenkins/job/master-onomondo-eim/a1=default,a2=default,a3=default,a4=default,label=osmocom-master/31/build5-deb12build-ansiblesrc/esipa_asn1_handler.erl1b43403ece8ccd4e80eaaca59dc364ec6910c89e1784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orges9p_client: convert InitiateAuthenticationOkEsipa to match SGP.32 V.1.2 In SGP.32 V.1.0.1, InitiateAuthenticationOkEsipa is almost identical to SGP.22 InitiateAuthenticationOkEs9. However, in SGP.32 V.1.2, the member euiccCiPKIdToBeUsed is renamed to euiccCiPKIdentifierToBeUsed. This means it is no longer possible to pass InitiateAuthenticationOkEsipa as InitiateAuthenticationOkEs9 to ES9+ directly. Instead we have to re-build the the InitiateAuthenticationOkEs9 from the contents of InitiateAuthenticationOkEsipa. Change-Id: I44c60a2f0d1129093ea67908d2eed167643a4a87 Related: SYS#8100 2026-07-14 11:53:08 +00001b43403ece8ccd4e80eaaca59dc364ec6910c89ees9p_client: convert InitiateAuthenticationOkEsipa to match SGP.32 V.1.2editsrc/esipa_asn1_handler.erlsrc/esipa_asn1_handler.erl63a9aa184a52e66571ae482e7abd31e1e695d3b91784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgesipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6 Section 2.11.2: eIM package result (EuiccPackageResult case) is now concatenated with PendingNotificationList instead of RetrieveNotificationsListResponse Section 5.14.6: ESipa.ProvideEimPackageResult: Significant change in parameters Change-Id: Ic0872edefc1844166943c60528557c6b7a6602ce Related: SYS#8100 2026-07-14 11:53:08 +000063a9aa184a52e66571ae482e7abd31e1e695d3b9esipa_asn1_handler: re-align to SGP.32 section 2.11.2 and section 5.14.6editsrc/esipa_asn1_handler.erlcontrib/tryme_configureImmediateEnable.shcontrib/tryme_configureAutoEnable.shsrc/esipa_rest_utils.erlcontrib/rest_api_response_schema.jsoncontrib/rest_api_resource_schema.json8a1256049cd8ba69bce7f41fc317889a339c216f1784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgesipa_rest_utils: re-align to SGP.32 Section 2.11.2 Section 2.11.2: rename EuiccPackageResultDataSigned.configureAutoEnableResult to EuiccPackageResultDataSigned.configureImmediateEnableResult Change-Id: Ib4e6a4b4cb4d26a391346169b9047515496dd308 Related: SYS#8100 2026-07-14 11:53:08 +00008a1256049cd8ba69bce7f41fc317889a339c216fesipa_rest_utils: re-align to SGP.32 Section 2.11.2editsrc/esipa_rest_utils.erldeletecontrib/tryme_configureAutoEnable.sheditcontrib/rest_api_resource_schema.jsoneditcontrib/rest_api_response_schema.jsonaddcontrib/tryme_configureImmediateEnable.shcontrib/rest_api_response_schema.jsoncontrib/rest_api_resource_schema.json7abf280e10af25a82cccb9abc7e8b19240a878511784029988000https://jenkins.osmocom.org/jenkins/user/laforgelaforgelaforge@osmocom.orgrest_api: move "required" member to the correct level In some locations in the JSON schema files we find the "required" member on the same level as the members of "properties" (likewise "items"). This is incorrect, the "required" member should always be on the same level as the "properties" or "items" member. (At the moment the JSON schema files serve only documentation purposes, they are not used to do any actual validation yet.) Change-Id: I07d51d0e809a718144bd51a6540ab51187bb4daa Related: SYS#8100 2026-07-14 11:53:08 +00007abf280e10af25a82cccb9abc7e8b19240a87851rest_api: move "required" member to the correct leveleditcontrib/rest_api_resource_schema.jsoneditcontrib/rest_api_response_schema.jsongithttps://jenkins.osmocom.org/jenkins/user/laforgelaforge