Article - CS431137

GetProperties with the "Automatically Update Values" option does not properly handle reconnections after a user session times out in ThingWorx Mashup and returns error "Rejecting NonceKey [<Key ID>] since it was not found in cache"

Modified: 04-Feb-2026   


Applies To

  • ThingWorx Platform 9.3

Description

  • After a user session times out or a platform restart, GetProperties with the Automatically Update Values option fails to properly handle reconnections
  • SecurityLog is flooded with Rejecting NonceKey [<Key ID>] since it was not found in cache errors
  • After reconnection, the mashup is calling every second (or even more frequently):
    • /Thingworx/Resources/EntityServices/Services/GetClientNonce, which returns an empty response
    • /Thingworx/WS with an obsolete nonce / appkey
    • /ThingworxStorage/logs/SecurityLog.log repeatedly reports below warning messages:
    • [L: WARN] [O: S.c.t.s.m.ApplicationKeyManager] [I: ] [U: ???] [S: ] [P: ] [T: https-jsse-nio-443-exec-129] *** ApplicationKey not found ***
      [L: ERROR] [O: S.c.t.s.m.NonceKeyManager] [I: ] [U: ???] [S: ] [P: ] [T: https-jsse-nio-443-exec-129] Rejecting NonceKey [<Key ID>] since it was not found in cache
  • The behavior varies depending on the browser vendor and whether SSO is used:
    • Chrome + Basic Auth (Authentication Dialog does not show on MacOS)
      • GetClientNonce is invoked every second and a new Basic Auth dialog pops up until credentials are provided
    • Firefox + Basic Auth
      • GetClientNonce is invoked once, the Basic Auth dialog pops up, and the Mashup is suspended until credentials are provided
    • All browser + SSO:

This is a printer-friendly version of Article 431137 and may be out of date. For the latest version click CS431137