dexter has submitted this change. ( https://gerrit.osmocom.org/c/onomondo-eim/+/43816?usp=email )
Change subject: esipa_asn1_handler: add TODO for missing confirmation code handling ......................................................................
esipa_asn1_handler: add TODO for missing confirmation code handling
The eIM implementation lacks the handling of a Confirmation Code, let's add a TODO for this.
Change-Id: I1265606549f9eb0872c7ea21407d651f34dc9eed --- M src/esipa_asn1_handler.erl 1 file changed, 5 insertions(+), 0 deletions(-)
Approvals: Jenkins Builder: Verified dexter: Looks good to me, approved
diff --git a/src/esipa_asn1_handler.erl b/src/esipa_asn1_handler.erl index f21d89f..b898850 100644 --- a/src/esipa_asn1_handler.erl +++ b/src/esipa_asn1_handler.erl @@ -121,6 +121,11 @@ % To simplify this we should automate this process by requesting and caching the IpaCapabilities once, % so that we the info within reach when we need it (similar to how we cache signPubKey, see also % mnesia_db_euicc.hrl). + % TODO: Implement Confirmation Code handling: This SM-DP+ does not support the handling of a + % confirmation code. To add support may add another field to the REST API, so that the REST API user + % may supply a confirmation code. Then we would calculate the Confirmation Code hash here and supply it + % with the hashCc field of authenticateClientOkDPEsipa. (the IPAd would then forward the contents of + % hashCc to the eUICC with the PrepareDownloadRequest). AuthenticateClientOkDPEsipa = AuthClntRespEs9#{ profileMetaData => StoreMetadataRequest },