
Modrinth · Minecraft mod
DevAuth Neo
Authenticate Minecraft accounts in development environments
Quick answer
Which DevAuth Neo release should I use?
DevAuth Neo 1.2.0 targets 26.3, 26.3-rc-1 with Fabric. It must be installed on the client. Do not install it on the dedicated server. No extra mods listed for this file.
Where it goes
Is DevAuth Neo required on the client, server, or both?
It must be installed on the client. Do not install it on the dedicated server.
This file is marked client-only.
What else does DevAuth Neo 1.2.0 need?
1.2.0. Change the file and its required mods may change too.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add DevAuth Neo without breaking your instance.
Built for DevAuth Neo 1.2.0. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 1.2.0. It targets 26.3, 26.3-rc-1 with Fabric; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
It must be installed on the client. Do not install it on the dedicated server.
- 04
Pick the file you checked
Use the “Get this file” button beside 1.2.0. It opens that exact file at the source.
About this project
What does DevAuth Neo add?
Authenticate Minecraft accounts in development environments.
This is a "reincarnation" of DevAuth but improved, updated and available directly as a Fabric mod.
Usage
Adding the mod
via Maven Central (default)
Add the following to build.gradle:
dependencies {
localRuntime 'net.litetex.mcm:dev-auth-neo:<version>'
// Further documentation: https://wiki.fabricmc.net/documentation:fabric_loom
}
via Modrinth
Add the following to build.gradle:
repositories {
// https://support.modrinth.com/en/articles/8801191-modrinth-maven
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
filter {
includeGroup 'maven.modrinth'
}
}
}
dependencies {
localRuntime 'maven.modrinth:dev-auth-neo:<version>'
// Further documentation: https://wiki.fabricmc.net/documentation:fabric_loom
}
Quickstart
IMPORTANT: DevAuth is disabled by default, in order to be unobtrusive.
The simplest way to enable it is by setting the corresponding system property: -Ddevauth.enabled=1
- When launching for the first time you will be prompted to enter your credentials
- You will also get hints on what to do in the console/logs when required
- After the authentication was successful the generated tokens will be stored in
microsoft_accounts.json- Future logins will try to reuse these tokens
- The tokens are then delegated to the game and it starts as usual
Configuration
The configuration is dynamically loaded from (sorted by highest priority)
- Environment variables
- prefixed with
DEVAUTH_ - all properties are in UPPERCASE and use
_instead of.or-
- prefixed with
- System properties
- prefixed with
devauth.
- prefixed with
- A configuration file located in
~/.dev-auth-neo/config.json
Full list of configuration options
General
| Property | Type | Default | Notes |
|---|---|---|---|
enabled |
bool |
false |
|
account |
String |
- | If not set: Will be prompted via the console |
account-type |
String |
microsoft |
Currently only Microsoft is supported |
force-handle-all-tokens-as-expired |
bool |
false |
Handles all existing tokens as if they have expired and refreshes them |
state-dir |
String |
Automatically determined~/.dev-auth-neo) |
The directory where the login information of the provider will be saved |
cache-profile-info-minutes |
int |
3606h |
How long should fetched profile information(uuid and name) be cached? |
Microsoft Grant-Flow options
NOTE: All grant-flow options are additionally prefixed with microsoft.oauth2.
For example predefined-provider must therefore be defined as devauth.microsoft.oauth2.predefined-provider
| Property | Type | Default | Notes |
|---|---|---|---|
grant-flow |
String |
auth-code-embedded |
See bellow for available flows |
client-id |
String |
automatically determined | Designed as general purpose override for e.g. a custom provider |
scopes |
List<String> |
automatically determined |
auth-code-embedded Auth Code flow using an embedded browser
- This login mechanism is identical to the one used by Minecraft's launcher
- Therefore selected by default
- This workflow downloads and installs a Chromium browser using CEF (Chromium Embedded Framework)
- The download is around 150MB
- It's installed by default into
~/.dev-auth-neo/jcef
| Property | Type | Default | Notes |
|---|---|---|---|
use-temporary-cache-dir |
bool |
true |
Creates and uses a temporary directory for the browser cache. If this is set to false all browser information (cookies, cache) and also possible logins will be persisted! |
redirect-uri |
String |
automatically determined | Designed as general purpose override for e.g. a custom provider |
auth-code-external Auth Code flow using an external browser
- Same as
auth-code-embeddedhowever this can be done with the system browser - Starts an integrated webserver to get the tokens at the end of the flow
- ⚠ This flow depends on 3rd party clients / launchers
- These clients are totally dependent on Mojangs explicit approval and can - although unlikely to happen - be blocked at any time for any reason by them
- The 3rd party can change or delete their client without warning
- The 3rd party might be able to see your login activity
- Available 3rd parties:
- DevAuth (default)
| Property | Type | Default | Notes |
|---|---|---|---|
predefined-provider |
String |
devauth |
|
open-system-browser |
bool |
true |
Should the system browser be automatically opened with the sign in page? |
redirect-port |
int |
automatically determined | Port used for the integrated webserver |
redirect-uri |
String |
automatically determined | Designed as general purpose override for e.g. a custom provider |
device-code Device Code flow
- This flow generates a short code that needs to be verified online with the an account
- ⚠ This flow depends on 3rd party clients / launchers
- These clients are totally dependent on Mojangs explicit approval and can - although unlikely to happen - be blocked at any time for any reason by them
- The 3rd party can change or delete their client without warning
- The 3rd party might be able to see your login activity
- Available 3rd parties:
| Property | Type | Default | Notes |
|---|---|---|---|
predefined-provider |
String |
multimc |
FAQ
How do I delete the login information?
Delete %USERPROFILE%\.dev-auth-neo (Windows) or ~/.dev-auth-neo (Linux)
I want to switch to another account
What's the easiest way to do this?
Set -Ddevauth.account=otherAccountName
Security?
The tokens are stored in a file on the disk in above specified folder.
As with all data on your PC, you as a user are responsible for keeping them secure.
You can revoke tokens in the Microsoft account settings.
Project description from Modrinth.
Pick your setup
DevAuth Neo by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
26.3
1 loader build26.2
1 loader build26.1.2
1 loader build26.1.1
1 loader build26.1-pre-1
1 loader build26.1
1 loader build1.21.11
1 loader buildCheck the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
DevAuth Neo versions and loaders
1.2.0
dev-auth-neo-1.2.0.jar
11 Sept 2026
1.1.1
dev-auth-neo-1.1.1.jar
31 May 2026
1.1.0
dev-auth-neo-1.1.0.jar
14 Mar 2026
1.0.2
dev-auth-neo-1.0.2.jar
22 Feb 2026
1.0.1
dev-auth-neo-1.0.1.jar
14 Dec 2025
1.0.0
dev-auth-neo-1.0.0.jar
14 Dec 2025
Looking for an older file? The official Modrinth project page is in Resources.