Authentication

Arc verifies player logins directly against your own server. This gives you control over who can play and keeps credential verification on your own server.

Configure a method

Open the Authentication tab for your client, add a method, and set its priority. Arc evaluates enabled methods in priority order. You can configure up to 10 methods, each with its own verification URL and launcher arguments.

  1. 01

    Choose Exchange Code or Password.

  2. 02

    Enter an HTTPS verification URL.

  3. 03

    Match the launcher arguments to your game.

Launcher arguments

The arguments below are examples. Configure each method's launcher arguments to match the flags your game uses. Arc never stores the credentials it receives from the launcher.

Exchange Code

For example, pass the one-time exchange code with -AUTH_PASSWORD.

-AUTH_PASSWORD <exchange-code>

Password

For example, pass the player's username and password with matching login and password arguments.

-AUTH_LOGIN <username>
-AUTH_PASSWORD <password>

Verify a login

When a player starts Arc, Arc sends their login details to the verification URL configured for the selected method. Your server decides whether the credentials are valid, then identifies the player in its response.

01

Receive

Arc sends the player details to your HTTPS endpoint.

02

Verify

Check the credentials and any challenge data on your server.

03

Identify

Return the verified player's identity with HTTP 200.

Request from Arc

{
  "token": "your-exchange-code",
  "challenge": "ok",
  "clientId": "your-client-id"
}

Response from your server

{
  "subject": "test",
  "displayName": "andrew"
}

HTTP 200: login accepted. Include subject and displayName in the response.

Any other status: login rejected.

Arc does not store the credentials it receives. Keep verification logic and account data on your server.