Article - CS339473

Unable to access Composer despite providing the correct User credentials with Idle Session Timeout set to 0 in ThingWorx Platform

Modified: 30-May-2023   


Applies To

  • ThingWorx Platform 8.5 to 9.3

Description

  • Composer suddenly became inaccessible, but Kepware data is still flowing to ThingWorx Platform
  • ThingWorx Platform always prompts for User credentials though the provided credentials are correct
  • User Management Subsystem > Idle Session Timeout got set to 0, how can this be corrected?
  • ThingWorx Composer suddenly stopped working and became inaccessible, despite providing correct credentials
  • What happens if we set the Idle Session Timeout configuration to 0?
  • ThingWorx Platform SecurityLog.log file located within <ThingworxStorage>\logs shows the following:
    • [L: WARN] [O: S.c.t.s.a.AuthenticationUtilities] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-3] Authentication attempt #1 FAILED for [user = Administrator]: Invalid Password
      [L: WARN] [O: S.c.t.s.a.ThingworxFormAuthenticator] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-3] Error on login attempt
      
      
      [L: WARN] [O: S.c.t.s.u.User] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-3] User: Administrator was LOCKED by service call
      [L: ERROR] [O: S.c.t.s.a.AuthenticationUtilities] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-3] User LOCKED after 6 login attempts for [user = Administrator] within 5 minutes
      [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-7] No authType or appKey parameter has been specified for Authentication Scheme: AUTH_THINGWORX_APPKEY
      [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-8] Authentication failed: Please make sure the credentials are correct.
      [L: ERROR] [O: S.c.t.s.a.AuthenticationFilter] [I: ] [U: ???] [S: ] [P: ] [T: https-openssl-nio-443-exec-8] Authentication failed: Please make sure the credentials are correct.
This is a printer-friendly version of Article 339473 and may be out of date. For the latest version click CS339473