Connect to local deployment KNIME HUB Failed

Installed KNIME Analytics Version 5.2, and set up mount point to connect to local deployment KNIME Business Hub, but return error in log file:

2024-02-01 11:03:32,253 : DEBUG : main : : DesktopAPI : : : Desktop API function successfully called: openWebUIPreferencePage
2024-02-01 11:03:35,887 : DEBUG : Thread-592 : : OAuthAuthenticator : : : Setting allowed clock skew for token parsing to 0s
2024-02-01 11:03:35,888 : DEBUG : Thread-592 : : OAuthAuthenticator : : : Login to ‘http://api.knimehub.xxx.xxx.xxx’.
2024-02-01 11:03:35,897 : INFO : Thread-592 : : OAuthAuthenticator : : : Opening browser to perform authentication for ‘http://api.knimehub.xxx.xxx.xxxx’.
2024-02-01 11:04:15,395 : DEBUG : qtp1329346973-859 : : OAuthAuthenticator : : : Tokens acquired.
2024-02-01 11:04:22,255 : DEBUG : main : : ExplorerServerContentProvider : : : Login to ‘knime-business-hub’ failed: JWT expired at 2024-02-01T11:03:55Z. Current time: 2024-02-01T11:04:15Z, a difference of 20398 milliseconds. Allowed clock skew: 0 milliseconds.
io.jsonwebtoken.ExpiredJwtException: JWT expired at 2024-02-01T11:03:55Z. Current time: 2024-02-01T11:04:15Z, a difference of 20398 milliseconds. Allowed clock skew: 0 milliseconds.
at io.jsonwebtoken.impl.DefaultJwtParser.parse(DefaultJwtParser.java:385)
at com.knime.explorer.server.rest.OAuthAuthenticator$OAuthRedirectHandler.extractUserInformation(OAuthAuthenticator.java:174)
at com.knime.explorer.server.rest.OAuthAuthenticator$OAuthRedirectHandler.handleRequest(OAuthAuthenticator.java:254)
at com.knime.explorer.server.rest.OAuthAuthenticator$OAuthRedirectHandler.handle(OAuthAuthenticator.java:222)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.Server.handle(Server.java:563)
at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:934)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1078)
at java.base/java.lang.Thread.run(Unknown Source)

The login screen as below:

And after key in username and password will redirect to below page:

Noticed that the URL as below:
http://auth.knimehub.xxx.xxx.xxx/auth/realms/knime/protocol/openid-connect/auth?response_type=code&client_id=analytics-platform&redirect_uri=http://127.0.0.1:57039/oauthredirectlistener&code_challenge_method=S256&code_challenge=rhVtjIu-BDRnZw05tfnunXe9isekNQH-T8U2g_sQoFk

And I checked configuration in KNIME Business hub, can’t find any setting related to 127.0.0.1

KNIME Business Hub service is ready as below:

Anyone can provide suggestion? Thanks

Hi @sylim ,

Welcome to the Forum! Thanks for extracting and sharing detailed logs. These are very helpful!

This line strikes me as interesting:
JWT expired at 2024-02-01T11:03:55Z. Current time: 2024-02-01T11:04:15Z, a difference of 20398 milliseconds. Allowed clock skew: 0 milliseconds.
I’m wondering whether the system clock may be out of sync. Can other users connect? If so, would you be able to right-click the time in the bottom right of your screen, select “Adjust date/time” and hit “Sync now” (c.f. alternative ways to sync time)?

image

Kind regards
Marvin

Hi Marvin,

I check on the pc also same result. May I know that the time sync issue will cause the URL redirect the URL to 127.0.0.1??

http://auth.knimehub.xxx.xxx.xxx/auth/realms/knime/protocol/openid-connect/auth?response_type=code&client_id=analytics-platform&redirect_uri=http://127.0.0.1:57039/oauthredirectlistener&code_challenge_method=S256&code_challenge=rhVtjIu-BDRnZw05tfnunXe9isekNQH-T8U2g_sQoFk

Or the time for the kubernetes Pod no sync? Can I know how to check the KNIME hub time sync config?

Hi @sylim ,

being redirected to 127.0.0.1 is quite common when signing in via OIDC within applications. Here, KNIME briefly starts up a local webserver in order to enable a correct and secure login.

In regards to the login issue: it still looks like this may be a time syncing issue. The error suggests that a token has expired for 20 seconds, though they should be valid for 5 minutes. Therefore, there may be a clock skew of 5 minutes and 20 seconds.

You can check the clients time by e.g. navigating to https://time.is/.
Could you check back with the IT team hosting KNIME Business Hub on whether the time there can be synced?
Should issues persist, I can also suggest reaching out to our enterprise support at support@knime.com or our support portal.

Kind regards
Marvin

Thanks Marvin,

After I check the time for KNIME Business Hub, manage to connect using KNIME analytics platform

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.