v0.3.5 — DATEV OAuth token exchange (client_secret_basic)
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.