diff --git a/SAS/TMSS/backend/src/tmss/authentication_backends.py b/SAS/TMSS/backend/src/tmss/authentication_backends.py
index 02c23d93d06fd9a096ab3302ff9aa4ede7e6c75b..0db2faea531d778ddb4588744c65c12f980e2a33 100644
--- a/SAS/TMSS/backend/src/tmss/authentication_backends.py
+++ b/SAS/TMSS/backend/src/tmss/authentication_backends.py
@@ -80,14 +80,12 @@ class TMSSOIDCAuthenticationBackend(OIDCAuthenticationBackend):
         logger.info('update user=%s claims=%s' % (user, claims))
         if not Token.objects.filter(user=user).first():
             Token.objects.create(user=user)  # required for websockets
-        try:
-            self._set_user_details_from_claims(user, claims)
-        except Exception as e:
-            logger.warning("Could not update user details from claims (%s)" % e)
-            # todo: apparently we can have the situation where an existing user account has the same username and there
-            #  (understandably) is a unique constraint on that field. So we cannot freely update these details.
-            #  Check why a Keycloak login does not match the existing entry and how we can best deal with that.
-            #  -> TMSS-2876
         self._set_user_project_roles_from_claims(user, claims)
         self._set_user_system_roles_from_claims(user, claims)
+        # todo: apparently we can have the situation where an existing user account has the same username and there
+        #  (understandably) is a unique constraint on that field. So we cannot freely update these details.
+        #  Check why a Keycloak login does not match the existing entry and how we can best deal with that.
+        #  -> TMSS-2876
+        # self._set_user_details_from_claims(user, claims)
+
         return user