Authnet Setup (Windows 5xx)

From Project Skyfire
Jump to navigation Jump to search

Authnet Setup (Windows 5xx)

Authnet is Project SkyFire's Battle.net-style authentication route for World of Warcraft: Mists of Pandaria 5.4.8, build 18414. It allows a supported, unmodified client to connect through the SkyFire Authnet Launcher. The launcher applies the required connection and trust changes in memory and does not permanently modify the game executable.

The classic authentication route remains available for compatible clients. Enabling Authnet does not disable the classic authserver listener.

Requirements

  • A current build of the SkyFire 5.4.8 server core.
  • A World of Warcraft 5.4.8 client at build 18414.
  • Windows x64 for the SkyFire Authnet Launcher.
  • A correctly configured authentication database and at least one realm in the realmlist table.
  • TCP port 1119 reachable by Authnet clients.
  • Each realm's world port reachable by clients. The usual worldserver port is TCP 8085.

Download the Authnet Launcher

The stable Windows installer is stored in the Community Tools repository:

Current package information:

Component Version or platform
Launcher 1.4 Authnet
Installer 1.4.1
Platform Windows x64
Supported client Mists of Pandaria 5.4.8, build 18414

The installer is self-contained and does not require a separate .NET runtime.

Server Administrator Setup

Configure authserver.conf

Use a current copy of authserver.conf.dist when creating or updating authserver.conf. Configure the Authnet listener as follows:

<syntaxhighlight lang="ini"> Authnet.Enabled = 1 Authnet.BindIP = "0.0.0.0" Authnet.Port = 1119 Authnet.VerboseLogging = 0 Authnet.AllowUnverifiedLogin = 0 Authnet.PasswordProofPrivateKey = "<matching-private-scalar>" </syntaxhighlight>

The value of Authnet.PasswordProofPrivateKey is a hexadecimal private scalar without a 0x prefix. It must match the public proof key installed in the client by the launcher build being distributed to players.

Do not publish, commit, or share the private scalar. Store it only in the deployed server configuration or provide it through the AUTHNET_PASSWORD_PROOF_PRIVATE_KEY environment variable.

The public Community Tools installer contains the Project SkyFire launcher proof key. A custom launcher build using a different public key requires its own matching server-side private scalar.

Keep Authnet.AllowUnverifiedLogin set to 0. Enabling it bypasses credential verification and must not be used as a connection workaround.

Leave the experimental Authnet.StartupModuleSeed, Authnet.StartupModuleName, and Authnet.StartupModuleKey settings at their defaults unless actively developing the protocol.

Configure worldserver.conf

Enable Authnet world-token resolution in worldserver.conf:

<syntaxhighlight lang="ini"> Authnet.WorldTokenResolve = 1 Authnet.VerboseLogging = 0 </syntaxhighlight>

This allows worldserver to resolve the temporary account token created during the Authnet realm handoff. Authentication warnings and errors remain logged while verbose tracing is disabled.

Configure realms and networking

Each enabled realm is read from the authentication database's realmlist table. Verify that:

  • The realm address is reachable from the player's computer.
  • The realm port matches the worldserver port, normally TCP 8085.
  • TCP 1119 is allowed through the server firewall for Authnet.
  • The realm world port is allowed through the firewall.
  • TCP 3724 is reachable when players will use launcher-based legacy account migration.

Restart authserver after changing realm records so the displayed realm list is refreshed. Start authserver and worldserver before testing a client login.

Account Setup

Authnet signs in with an email address. New accounts should be created with an email, legacy username, and password so all required password verifiers are generated.

From the worldserver console:

<syntaxhighlight lang="text"> account create player@example.com PLAYER password </syntaxhighlight>

From an authorized in-game GM account, prefix the same command with a period:

<syntaxhighlight lang="text"> .account create player@example.com PLAYER password </syntaxhighlight>

Replace all example values before running the command. Players use the email address, not the legacy username, on the Authnet login screen.

Existing accounts

An older account may not have the native verifier required by Authnet. Use either of these methods:

  1. Use the launcher's Migrate Account to Email Login tool.
  2. Reset the account password from the worldserver console to regenerate its password verifiers:

<syntaxhighlight lang="text"> account set password USERNAME newpassword newpassword </syntaxhighlight>

The account must also have a valid, unique email address. Do not enable unverified login to work around a missing verifier.

Install the Launcher

  1. Close the game client and any older SkyFire Launcher instance.
  2. Download and run SkyFireLauncherSetup.msi.
  3. Approve the Windows installation prompt.
  4. Choose whether to install the optional desktop shortcut.
  5. Finish the installation and open SkyFire Launcher from the Start menu or desktop shortcut.

Running a newer installer upgrades the existing installation. The launcher can be removed through Windows Installed Apps.

Configure the Launcher

  1. Open SkyFire Launcher.
  2. Select the gear icon to open Configuration.
  3. Set Client Location to the root of the 5.4.8 client folder containing Wow.exe and Wow-64.exe.
  4. Select the default 32-bit or 64-bit client.
  5. Set Login Address to the hostname or IP address supplied by the server administrator. Enter only the host or IP unless the administrator specifically provides a different format.
  6. Enable Authnet login.
  7. Optionally enable Clear client cache on each login while testing server or database changes.
  8. Select Save.

Disabling Authnet login returns the launcher to its standard client route. That route still requires a server and client combination that supports classic authentication.

Migrate a Legacy Account

  1. Open the launcher's Configuration page.
  2. Select Migrate Account to Email Login.
  3. Enter the existing username and current password.
  4. Enter the new email address and the new password twice.
  5. Select Migrate.

Migration requires a compatible, running authserver and a valid existing account. After migration, use the email address and new password in the game client.

Launch and Sign In

  1. Start SkyFire Launcher.
  2. Select the 32-bit or 64-bit client.
  3. Select Play.
  4. Enter the account email address and password in the game client's login fields.
  5. Select a realm and continue to the character list.

The launcher does not collect the player's game password during normal login. Credentials are entered once in the game client.

When using an unmodified client, always start the game through SkyFire Launcher. Starting Wow.exe or Wow-64.exe directly skips the temporary routing and trust changes and may send the client to its original service endpoints.

Verification

A working setup should complete these stages:

  1. Authserver starts an Authnet listener on TCP 1119.
  2. Correct email credentials pass authentication; an incorrect password is rejected.
  3. The client receives the database-backed realm list.
  4. Selecting a realm opens the character list.
  5. Entering a character connects to worldserver normally.

Troubleshooting

Error 114 or Unable to Connect

  • Confirm the launcher has Authnet login enabled.
  • Confirm Login Address contains the correct server hostname or IP address.
  • Confirm authserver is running with Authnet.Enabled = 1 and is listening on TCP 1119.
  • Confirm Windows Firewall, the router, and any hosting firewall allow TCP 1119.
  • Make sure the client was started with the launcher's Play button.

Immediate Disconnect After Entering Credentials

  • Confirm the player entered the account email address and correct password.
  • Migrate the legacy account or reset its password to create the native Authnet verifier.
  • Check authserver for a missing-verifier message.
  • Confirm Authnet.PasswordProofPrivateKey is valid and matches the launcher build's public proof key.
  • Keep Authnet.AllowUnverifiedLogin = 0.

Stuck on Success or Retrieving Realm List

  • Confirm worldserver is running with Authnet.WorldTokenResolve = 1.
  • Confirm authserver and worldserver use the same authentication database.
  • Check the realmlist table for the selected realm's address and port.
  • Confirm the realm's world port is reachable from the client computer.
  • Restart authserver after adding or changing realm records.

Client Starts Against the Original Service

Close the client and start it again from SkyFire Launcher. An unmodified client started directly does not receive the launcher's in-memory endpoint changes.

Client Executable Not Found

Confirm Client Location points to the client root and that the selected Wow.exe or Wow-64.exe exists there.

Stale Client Data or UI Problems

Enable Clear client cache on each login, save the launcher configuration, close the client completely, and launch it again.

Diagnostic Logging

For a short troubleshooting session, verbose Authnet logging can be enabled independently in each server configuration:

<syntaxhighlight lang="ini">

  1. authserver.conf

Authnet.VerboseLogging = 1

  1. worldserver.conf

Authnet.VerboseLogging = 1 </syntaxhighlight>

Return both settings to 0 after collecting the required logs to avoid excessive console output.

License

SkyFire Launcher is distributed under the GNU General Public License version 3. The source code and full license are available in the launcher repository.

Copyright (c) 2026 Project SkyFire.

Retrieved from "https://wiki.projectskyfire.org/index.php?title=Authnet_Setup_(Windows_5xx)&oldid=1284"