Developer Authentication

A tool to manage login status during development.

1 min to read

The Developer Authentication Tool acts as a stand-in for the Epic Games Store launcher during game development. It improves iteration time by enabling developers to log in once and remain logged in, even after closing and relaunching the game. Additionally, the Developer Authentication Tool can store credentials for multiple users, so developers can run multiple instances of a game to test multiplayer scenarios.

Conceptually, the tool is a combination of a web browser and a server. The web browser portion provides the user interface, including the account portal page. The server portion responds to requests initiated by the SDK, when the EOS_Auth_Login function is called with the EOS_LCT_Developer login credential type.

You can find the Developer Authentication Tool in the SDK/Tools folder within the Epic Online Services SDK download archive. See the EOS Get Started documentation for information about downloading and setting up the SDK.

Note: To use Epic Online Services (EOS) SDK, your local network, router, and firewall must allow access to specific host addresses. For a complete list of these host addresses, see the Firewall Considerations documentation.

Tool and SDK Interaction

  1. When launching the application, you must enter a TCP port number to listen for EOS SDK login requests.
  2. Login using the Epic Games Account Portal, providing email, password, and multi-factor authentication when prompted.
  3. After the Authentication Tool receives an Auth Token, give the credentials a name.
  4. After you have one or more named credentials, you may repeatedly call EOS_Auth_Login using the EOS_LCT_Developer login credential type.

Using the Developer Login Credential Type

Requests made through the tool use the Developer Login Credential Type (EOS_LCT_Developer). Call EOS_Auth_Login with the EOS_Auth_Credentials structure initialized as follows:

TypeSet this to EOS_LCT_Developer.
IdThis string should contain the host and port where your Authentication Tool is running. For example, if you chose port 6547 and the Authentication Tool is running locally, Id should be "localhost:6547".
TokenThis should be the name you provided for the credential after logging into the Authentication Tool.