EVE Online SSO site

Table of contents

• Using SSO
  • Authorization Flow
• Importing Data from the ESI

Documentation

Using Single Sign-On

Authorization Flow

1. The user will navigate to http://localhost/auth/login, which will redirect the user to the EVE SSO authorization server. The request to the EVE SSO authorization server will contain the following query parameters:

   • response_type=code
   • redirect_uri=<app-callback-url>
   • client_id=<app-client-id>
   • scope=<space-delimited-scopes>
   • state=<random-string>

2. The user will log in with their specified EVE online account and character, EVE SSO will then make a GET request to the callback URL provided (redirect_uri), containing a single-use authorization code that expires in 5 minutes from the time of issue.

3. The callback endpoint will retrieve the authorization code from the request and make a POST request to https://login.eveonline.com/v2/oauth/token with a payload containing the code, using Basic authentication where the application's client ID is the username and the client secret key is the password.

4. EVE SSO will respond with a JSON payload containing a JWT access token and a refresh token that looks like this:

   {
     "access_token": <JWT token>,
     "expires_in": 1199,
     "token_type": "Bearer",
     "refresh_token": <unique string>
   }
   

5. The callback endpoint will retrieve the JSON payload and validate the access token, see docs for more details on how this validation is performed.

6. The callback endpoint will make an authenticated GET request to https://login.eveonline.com/oauth/verify. EVE SSO will respond with a JSON payload containing authenticated character information that looks like this:

   {
     "CharacterID": 96542725
     "CharacterName": "Solomon Kaldari"
     "ExpiresOn": "2024-07-04T18:11:20"
     "Scopes": "esi-alliances.read_contacts.v1 esi-assets.read_assets.v1..."
     "TokenType": "Character"
     "CharacterOwnerHash": "HxZWS89g1jAdT3gagRypEadDMm4="
     "IntellectualProperty": "EVE"
   }
   

7. A new user session will be created for the authenticated character with relevant access permissions depending on the character's corporation and assigned roles.

Useful Links

• Crowd-sourced documentation
• EVE Swagger Interface
• EVE Developers