2.2 KiB
Authentication
Why Authentication
Minecraft is the most Popular game out there, And is is very easy to play it without paying for it. In Fact you don't pay for the Game, You pay for an Minecraft Account. People who don't bough the Game but play online are using Cracked Accounts
Cracked Accounts
- Don't cost any Money
- Everyone can set their own Nickname
- Have no UUID
- Have no Skin/Cape
- Not Secure
The Problem is that everyone can name themself how they want, Allowing to Join the Server as a Staff Member for example and having extended permissions, Cracked accounts are also often used for Botting and Denial of Service Attacks.
Cracked Server
By default the online_mode is enabled in the configuration, This enables Authentication disallowing Cracked Accounts. When you are willing to allow Cracked Accounts, you can dissable online_mode
in the configuration.toml
How Mojang Authentication works
To ensure a player has a premium accounts:
- A client with a premium account sends a login request to the Mojang session server.
- Mojang's servers verify the client's credentials and add the player to the their Servers
- Now our server will send a Request to the Session servers and check if the Player has joined the Session Server.
- If the request was successfull, It will give use more information about the Player (e.g. UUID, Name, Skin/Cape...)
Custom Authentication Server
Pumpkin does support custom Authentication servers, You can replace the Authentication URL in features.toml.
Pumpkin Authentication works like this (Mojang/Custom):
-
GET Request > Authentication
-
Status Code 200 > Successfull
-
Successfull > Parse JSON Game Profile
Game Profile
id: UUID
name: String
properties: Array<Property>
Important
Optional, Only present when actions are taken
profile_actions: Array<ProfileAction>
Property
name: String
Important
base 64
- value: String
Important
Optional, base 64
- signature: String
Profile Action
FORCED_NAME_CHANGE
USING_BANNED_SKIN