# Knowledge Base: Why does a OAuth2 client get invalid\_client from the EOS request token endpoint when the client secret contains special characters? 

**URL:** <https://forums.unrealengine.com/t/knowledge-base-why-does-a-oauth2-client-get-invalid-client-from-the-eos-request-token-endpoint-when-the-client-secret-contains-special-characters/2858127>\
**Category:** Tutorial & Course Discussions\
**Tags:** epic-online-services\
**Created:** [November 18, 2026, 6:26am UTC](https://forums.unrealengine.com/t/knowledge-base-why-does-a-oauth2-client-get-invalid-client-from-the-eos-request-token-endpoint-when-the-client-secret-contains-special-characters/2858127 "2026-11-18T06:26:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SebBergy2.0](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/sebbergy2.0/32/1214708_2.png) [@SebBergy2.0](https://forums.unrealengine.com/u/SebBergy2.0)\
**Post date:** [November 18, 2026, 6:26am UTC](https://forums.unrealengine.com/t/knowledge-base-why-does-a-oauth2-client-get-invalid-client-from-the-eos-request-token-endpoint-when-the-client-secret-contains-special-characters/2858127/1 "2026-11-18T06:26:33Z")

</div>

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](http://golang.org/x/oauth2) 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](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)
