From 7b524fa079f8b166eb905befe0f84f181106c109 Mon Sep 17 00:00:00 2001
From: Philipp Maier <pmaier@sysmocom.de>
Date: Fri, 15 Mar 2024 09:22:28 +0100
Subject: [PATCH] osmo-smdpp: fix generation of transactionId

The hex string of the generated transactionId contains lowercase hex
digits. However SGP.22 explicitly spcifies to use uppercase hex digits
when using JSON fromatted messages. See section 6.5.2.6 for example.

Related: SYS#6720
Change-Id: I8439aa9d70f6fe798fa88b623bac13debdc19ca1
---
 osmo-smdpp.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/osmo-smdpp.py b/osmo-smdpp.py
index 582b2222..1f4311da 100755
--- a/osmo-smdpp.py
+++ b/osmo-smdpp.py
@@ -239,7 +239,7 @@ class SmDppHttpServer:
 
         # Generate a TransactionID which is used to identify the ongoing RSP session. The TransactionID
         # SHALL be unique within the scope and lifetime of each SM-DP+.
-        transactionId = uuid.uuid4().hex
+        transactionId = uuid.uuid4().hex.upper()
         assert not transactionId in self.rss
 
         # Generate a serverChallenge for eUICC authentication attached to the ongoing RSP session.