This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+14 more
Affected surfaces
Summary
AI summaryFixed DATEV connector OAuth token exchange by using HTTP Basic auth for the token endpoint.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Fixes DATEV connector OAuth token exchange by using HTTP Basic auth for client credentials. Fixes DATEV connector OAuth token exchange by using HTTP Basic auth for client credentials. Source: llm_adapter@2026-07-17 Confidence: low |
— |
Full changelog
Fixes
- DATEV connector OAuth token exchange (#419): DATEV's token endpoint requires HTTP Basic client authentication (
WWW-Authenticate: Basic) and rejects body-supplied credentials with401 invalid_client. The connector authorization-code exchange previously sentclient_id/client_secretonly in the request body, so every DATEV confidential client failed at the token step. Added a per-connectortokenAuthMethod(basic| defaultpost); the DATEV adapter now usesbasic, applied to both the initial code exchange and token refresh. Default behaviour is unchanged for all other connectors.
Verification: confirmed read-only against DATEV's sandbox token endpoint (correct per DATEV's own OIDC discovery); backend typecheck + lint clean; connector OAuth tests 22/22 (3 new).
Note: a valid DATEV client secret is still required end-to-end — this release fixes the authentication method that was blocking all DATEV token exchanges.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About AnythingMCP
All releases →Beta — feedback welcome: [email protected]