You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UiPath access tokens are not guaranteed to be JWTs — Coded Agents can
authenticate with opaque tokens (e.g. reference tokens). PlatformSettings
previously rejected any non-JWT token at construction with "Invalid
access token: expected JWT with at least 2 dot-separated parts" because
validation assumed every token is a JWT.
Token introspection is now best-effort, with no assumptions about token
shape (no prefix sniffing):
- Add try_parse_access_token(), which returns the JWT payload or None.
- is_token_expired() returns False when the token is not a parseable JWT.
- The settings validator only extracts client_id when the token parses
as a JWT; otherwise client_id stays None.
Bumps core and langchain to 1.13.1.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,11 @@
2
2
3
3
All notable changes to `uipath_llm_client` (core package) will be documented in this file.
4
4
5
+
## [1.13.1] - 2026-06-09
6
+
7
+
### Fixed
8
+
-`PlatformSettings` now accepts non-JWT access tokens (e.g. opaque UiPath reference tokens) for `UIPATH_ACCESS_TOKEN`. Previously any token that was not a parseable JWT failed validation with "Invalid access token: expected JWT with at least 2 dot-separated parts". Token introspection is now best-effort: `is_token_expired` returns `False` when the token is not a parseable JWT, and the settings validator only extracts `client_id` when the token is a parseable JWT. Added `try_parse_access_token` helper in `uipath.llm_client.settings.platform.utils`.
Copy file name to clipboardExpand all lines: packages/uipath_langchain_client/CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,11 @@
2
2
3
3
All notable changes to `uipath_langchain_client` will be documented in this file.
4
4
5
+
## [1.13.1] - 2026-06-09
6
+
7
+
### Fixed
8
+
- Picks up the core `uipath-llm-client` 1.13.1 fix allowing non-JWT access tokens (e.g. opaque UiPath reference tokens) as `UIPATH_ACCESS_TOKEN`, so LangChain clients built on `PlatformSettings` no longer fail validation with "Invalid access token: expected JWT with at least 2 dot-separated parts".
0 commit comments