The EOS token endpoint at /auth/v1/oauth/token does not URL-decode the credentials inside the Basic Authorization header. RFC 6749 section 2.3.1 requires clients to URL-encode client_id and client_secret before base64-encoding them, so spec-compliant libraries (such as The Go Programming Language and…
https://dev.epicgames.com/community/learning/knowledge-base/p4JdY/epic-online-services-why-does-a-oauth2-client-get-invalid_client-from-the-eos-request-token-endpoint-when-the-client-secret-contains-special-characters