Token parsing error with Logto OIDC integration

Description

When attempting to use OIDCWarden with Logto as the OIDC provider, the token endpoint fails to parse the response with the following error:

Failed to contact token endpoint: Parse(Error { path: Path { segments: [] }, original: Error("Failed to parse payload JSON: Error("invalid type: null, expected a string", line: 1, column: 371)", line: 1, column: 878) }

The token response appears to be valid JSON containing access_token, expires_in, and id_token fields, but the parser is expecting a string where it's finding a null value.

Environment

OIDCWarden version: latest (v2024.10.2-3)
OIDC Provider: Logto - https://github.com/logto-io/logto
OIDC Redirect URIs: https://MY_OIDCWARDEN.COM/identity/connect/oidc-signin
Deployment method: Docker (timshel/oidcwarden:latest)

Configuration

SSO_ENABLED=true
SSO_AUTHORITY=https://MY_LOGTO.com/oidc
SSO_SCOPES=openid profile email offline_access
SSO_PKCE=false
SSO_ALLOW_UNKNOWN_EMAIL_VERIFICATION=true
SSO_DEBUG_TOKENS=true

Steps to reproduce

Configure OIDCWarden with Logto as the OIDC provider
Attempt to log in via SSO
Authentication with Logto succeeds
Token exchange fails with parsing error

Related information

This appears to be similar to the Auth0 timestamp parsing issue mentioned in the documentation that requires the accept-rfc3339-timestamps feature flag.

Timshel / OIDCWarden