1. 主页
  2. 支持
技术文章 - CS339473

尽管在 ThingWorx Platform 中提供了将空闲会话超时设置为 0 的正确用户凭据，但仍无法访问 Composer

已修改: 30-May-2023   


注意：本文已使用机器翻译软件翻译，以方便非英语客户阅读。但翻译内容可能包含语法错误或不准确之处。请注意， PTC对本文所含信息的翻译准确性及使用后果不承担任何责任。请在 此处 查看本文的英文原始版本以便参考。有关机器翻译的更多详情，请单击 此处 。
感谢您告诉我们。我们将尽快审阅此译文。

适用于

  • ThingWorx Platform 8.5 to 9.3

说明

  • Composer 突然无法访问，但 Kepware 数据仍在流向 ThingWorx Platform
  • 尽管提供的凭据正确，但 ThingWorx Platform 始终提示输入用户凭据
  • User Management Subsystem > Idle Session Timeout设置为 0，如何更正？
  • 尽管提供了正确的凭据，但 ThingWorx Composer 突然停止工作并变得无法访问
  • 如果我们将空闲会话超时配置设置为 0 会发生什么？
  • 位于<ThingworxStorage>\logs中的 ThingWorx Platform SecurityLog.log文件显示以下内容：
    • [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.
这是文章 339473 的 PDF 版本，可能已过期。最新版本 CS339473