From aa5d50322e770e6e146fa3b13c2cfa42ec30b251 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 6 Mar 2026 17:41:49 +0000 Subject: [PATCH 1/2] Initial plan From 70e4553ef4d75730587e76cda45d8455f0019a44 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 6 Mar 2026 17:44:21 +0000 Subject: [PATCH 2/2] Add warning about deprecated openStreamingConnection not compatible with JWT Co-authored-by: marcelomendoncasoares <6807059+marcelomendoncasoares@users.noreply.github.com> --- .../05-token-managers/02-jwt-token-manager.md | 4 ++++ .../05-token-managers/02-jwt-token-manager.md | 4 ++++ .../05-token-managers/02-jwt-token-manager.md | 4 ++++ .../05-token-managers/02-jwt-token-manager.md | 4 ++++ .../05-token-managers/02-jwt-token-manager.md | 4 ++++ .../05-token-managers/02-jwt-token-manager.md | 4 ++++ 6 files changed, 24 insertions(+) diff --git a/docs/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/docs/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index a46dc86d..2ef2a22e 100644 --- a/docs/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/docs/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -206,3 +206,7 @@ await TokenMetadata.db.insertRow( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +::: diff --git a/versioned_docs/version-3.0.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/versioned_docs/version-3.0.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index 2082a80d..567dba84 100644 --- a/versioned_docs/version-3.0.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/versioned_docs/version-3.0.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -109,3 +109,7 @@ final jwtConfig = JwtConfigFromPasswords( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +::: diff --git a/versioned_docs/version-3.1.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/versioned_docs/version-3.1.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index 2082a80d..567dba84 100644 --- a/versioned_docs/version-3.1.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/versioned_docs/version-3.1.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -109,3 +109,7 @@ final jwtConfig = JwtConfigFromPasswords( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +::: diff --git a/versioned_docs/version-3.2.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/versioned_docs/version-3.2.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index 2082a80d..567dba84 100644 --- a/versioned_docs/version-3.2.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/versioned_docs/version-3.2.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -109,3 +109,7 @@ final jwtConfig = JwtConfigFromPasswords( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +::: diff --git a/versioned_docs/version-3.3.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/versioned_docs/version-3.3.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index 2082a80d..567dba84 100644 --- a/versioned_docs/version-3.3.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/versioned_docs/version-3.3.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -109,3 +109,7 @@ final jwtConfig = JwtConfigFromPasswords( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +::: diff --git a/versioned_docs/version-3.4.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md b/versioned_docs/version-3.4.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md index a46dc86d..2ef2a22e 100644 --- a/versioned_docs/version-3.4.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md +++ b/versioned_docs/version-3.4.0/06-concepts/11-authentication/05-token-managers/02-jwt-token-manager.md @@ -206,3 +206,7 @@ await TokenMetadata.db.insertRow( ## Client-side configuration When using the `JwtTokenManager` in the server, no extra configuration is needed on the client. It will automatically include the access token in requests to the server and eagerly refresh the token when it is 30 seconds away from expiring. In case the refresh token expires, the client will automatically sign the user out and redirect to the login page. + +:::warning +The deprecated `client.openStreamingConnection()` interface is not compatible with JWT authentication. If you are using JWT tokens, migrate to [streaming endpoints](/concepts/streams) instead. +:::