Description
BeaconAuth adds a secure sign-in layer for Minecraft communities. It connects a Minecraft server to a self-hosted BeaconAuth web service, allowing server owners to require web-based authentication for modded clients while keeping account verification clear, configurable, and under their own control.
Features
- Web-based Minecraft login flow
- OAuth and passkey support through the BeaconAuth server
- Signed session verification with JWT and JWKS
- Configurable server-side authentication behavior
- Support for community-managed BeaconAuth accounts
- Localized client messages
- No third-party analytics, advertising, telemetry, or external file downloads in the Minecraft mod
How it works
When a player joins a server that uses BeaconAuth, the mod can open the configured BeaconAuth login page in the player’s browser. After the login is completed, the mod returns a signed authentication result to the Minecraft server, where it is verified against the configured BeaconAuth server keys.
Server owners host and configure their own BeaconAuth server URL.
Supported versions
| Minecraft version | Fabric | Forge | NeoForge |
|---|---|---|---|
| 1.20.1 | Yes | Yes | No |
| 1.21.1 | Yes | No | Yes |
| 1.21.8 | Yes | No | Yes |
Install the jar that matches your Minecraft version and loader from the Files tab.
Privacy and network usage
The Minecraft mod connects to the BeaconAuth server configured by the server owner during the login flow. It does not include ads, analytics, telemetry, or background file downloads.
The client may open the configured BeaconAuth web page in the player’s browser and use a temporary local callback listener to complete the login flow.
Server owners are responsible for their own BeaconAuth deployment, logs, OAuth provider configuration, and community privacy notice.
License
BeaconAuth is licensed under the MIT License.