Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EpicGames Provider #766

Open
10GeekJames opened this issue Mar 12, 2023 · 1 comment
Open

EpicGames Provider #766

10GeekJames opened this issue Mar 12, 2023 · 1 comment

Comments

@10GeekJames
Copy link

Which provider would you like support added for?

EpicGames

Provider Documentation

https://dev.epicgames.com/docs/epic-account-services/auth/auth-interface

Are you willing to implement this provider yourself?

Possibly

Additional context

They have recently launched a developer program that will likely bring much more attention to this needed behavior

@kevinchalet
Copy link
Member

kevinchalet commented Mar 17, 2023

I added Epic Games to the OpenIddict client stack and I didn't hit any major issue. Two remarks tho' if you're interested in contributing:

  • Even if it's not explicitly mentioned, Epic Games supports OpenID Connect (but doesn't list openid as a supported scope in its configuration/discovery document) and exposes a standard userinfo endpoint.
  • The basic client authentication method is not standard: you can't formURL-encode the client credentials (as required by the specification) before base64-encoding them. And of course, they do include things like / or + in their client secrets... 🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants