DevAuth Neo

Add the following to build.gradle:

dependencies {
    localRuntime 'net.litetex.mcm:dev-auth-neo:<version>'
    // Further documentation: https://wiki.fabricmc.net/documentation:fabric_loom
}

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
}

• Environment variables
  • prefixed with DEVAUTH_
  • all properties are in UPPERCASE and use _ instead of . or -
• System properties
  • prefixed with devauth.
• A configuration file located in ~/.dev-auth-neo/config.json

General

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

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

auth-code-external Auth Code flow using an external browser

• Same as auth-code-embedded however 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)

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:
    • MultiMC (default)
    • DevLogin
    • Prism