How goldengr/authserver works
golden’s AuthServer is a Minecraft login backend: a client completes the server handshake and encryption exchange, the server checks the session with Microsoft’s authentication service, then issues a code for use in an app. The code is passed to a configurable token-logging hook; persistence is left to the operator’s backend. The server also provides status responses and configurable connection limits and server messages. The excerpts show these responsibilities concentrated in src/main.py; they do not expose every handler or the implementation of rate limiting.
Main entry points: main.py Session check · server.properties Server properties · logTokens.py Token hook
Components 13
Login flow
- Protocol handling
src/main.py - Encryption exchange
src/main.py - Session check
src/main.py - Code issuance
src/main.py - Code message
src/main.py
Server features
- Status response
src/main.py - Connection limits
src/main.py - Server factory
src/main.py
Configuration
- Server properties
src/server.properties
Integrations
- Token hook
src/logTokens.py - Backend database
- Microsoft auth
Other components
- Minecraft client
Connections 13
- Minecraft client → Protocol handling: connects to
README.md - Protocol handling → Encryption exchange: handles login
src/main.py - Encryption exchange → Session check: checks session
src/main.py - Session check → Microsoft auth: requests validation
src/main.py - Session check → Code issuance: continues on success
src/main.py - Code issuance → Token hook: logs token
src/main.py - Token hook → Backend database: persists token
- Code issuance → Code message: formats code
src/main.py - Code message → Minecraft client: sends code
README.md - Minecraft client → Status response: requests status
src/main.py - Server factory → Protocol handling: selects protocol
src/main.py - Server properties → Server factory: configures server
README.md - Server properties → Connection limits: sets limits
README.md