BedrockPassport

🪪 BedrockPassport 1.1.1

BedrockPassport 1.1.1 adds recovery controls for saved Java-account sign-ins without removing Passport identities or breaking the normal seamless reconnect flow.

🔐 Saved login recovery

Server administrators can now invalidate stored JAVA_ACCOUNT authentication state when needed.

A reset does not delete the saved Passport identity, Java UUID, player data, inventory, permissions, statistics, or other server-side data.

🎯 Reset one Java account

/bp reset-login <javaName>

This removes the saved reusable authentication state for the matching Java account.

The next time that account is selected, the player is asked to authenticate with Microsoft/Minecraft again. BedrockPassport only accepts the re-authentication if it resolves to the same Java UUID that is already saved in the Passport.

After successful verification, the new auth state is stored again and normal saved-account reconnects continue as before.

🌐 Reset all saved Java sign-ins

/bp reset-login --all confirm

This:

• removes all saved JAVA_ACCOUNT credentials;
• rotates the local credentials.key;
• keeps all Passport identities and saved Java UUID mappings intact.

Affected players verify their existing Java account once on the next connection, then normal saved-account reuse resumes.

🛡 Safer reset handling

• Credential resets are blocked while an online Passport selector is active.
• New selectors are temporarily blocked while a credential reset is in progress.
• Global reset reports partial failure if credentials were deleted but the encryption key could not be rotated.
• Point resets match Java account names case-insensitively.
• Missing credentials now lead into the existing re-authentication flow instead of removing the account.

🧹 Other changes

• Improved admin command usage text.
• Kept the existing LOCAL and JAVA_ACCOUNT behavior unchanged outside of the new recovery controls.