1. Home
  2. Support
Article - CS304489

Authentication configuration error is reported after configuring ThingWorx Navigate SSO with PingFederate as IdP

Modified: 15-Sep-2023   


Applies To

  • Windchill Navigate (formerly ThingWorx Navigate) 1.8.0 to 1.9.0

Description

  • Authentication configuration error is reported after configuring ThingWorx Navigate SSO with PingFederate as IdP
  • After inputting username and password, following error is seen from web browser:

The system is currently encountering an authentication configuration error.
Close the browser and try to login again. If the problem persists, contact your system administrator.

User-added image
  • ThingWorx application log reports following error:
    2019-04-11 01:59:33.612+0000 [L: WARN] [O: c.t.c.s.c.j.Jsr356ServerConnection] [I: ] [U: ] [S: ] [T: https-jsse-nio-8443-exec-2] Server WebSocket closed unexpectedly and has already been unregistered from Server Endpoint [ws session id: 0] Unable to unwrap data, invalid status [CLOSED]
    2019-04-11 02:00:23.347+0000 [L: ERROR] [O: c.t.s.a.AuthenticationFilter] [I: ] [U: ] [S: ] [T: https-jsse-nio-8443-exec-4] Could not handle request
  • Integration Runtime log reports following error:
2019-11-04 01:59:32.409 [Client-EndpointMonitor-1] ERROR c.t.c.c.c.n.NettyClientConnectionFactory - Exception occurred while connecting to server
java.util.concurrent.TimeoutException: timeout waiting for websocket handshake to complete
    at com.thingworx.communications.client.connection.netty.NettyClientConnectionFactory$HandshakeCompletionNotifier.await(NettyClientConnectionFactory.java:693)
    at com.thingworx.communications.client.connection.netty.NettyClientConnectionFactory.createConnection(NettyClientConnectionFactory.java:398)
    at com.thingworx.communications.client.endpoints.ClientCommunicationEndpoint.refillConnections(ClientCommunicationEndpoint.java:230)
    at com.thingworx.communications.common.endpoints.monitor.ConnectivityMonitorTask.dutyCycleOn(ConnectivityMonitorTask.java:159)
    at com.thingworx.communications.common.endpoints.monitor.ConnectivityMonitorTask.run(ConnectivityMonitorTask.java:306)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
2019-11-04 01:59:32.534 [vert.x-worker-thread-4] WARN  c.t.i.ThingworxEdgeVerticle - Client did not connect within 30 seconds. Exiting
2019-11-04 01:59:32.816 [Client-EndpointMonitor-1] INFO  c.t.c.c.c.n.NettyClientConnectionFactory - forcing underlying tcp channel closed [is open: true, is active: true]
2019-11-04 01:59:33.565 [Client-EndpointMonitor-1] ERROR c.t.c.c.e.ClientCommunicationEndpoint - Refilling connections on [endpoint 0, uri: wss://xxxxx.xxxx.xxx.xxx:8443/Thingworx/WS] failed : timeout waiting for websocket handshake to complete
2019-11-04 01:59:32.846 [vert.x-eventloop-thread-0] ERROR c.t.i.Entrypoint - Failed to deploy ThingWorx Edge Verticle; retrying in 10 seconds
java.nio.channels.NotYetConnectedException: null
    at com.twx.integration.ThingworxEdgeVerticle.createVirtualThing(ThingworxEdgeVerticle.java:170)
    at com.twx.integration.ThingworxEdgeVerticle.start(ThingworxEdgeVerticle.java:140)
    at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:494)
    at io.vertx.core.impl.ContextImpl.executeTask(ContextImpl.java:320)
    at io.vertx.core.impl.WorkerContext.lambda$wrapTask$0(WorkerContext.java:34)
    at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
    at java.lang.Thread.run(Thread.java:748)
This is a printer-friendly version of Article 304489 and may be out of date. For the latest version click CS304489