This commit added a simple check that check spigot.yml -> settings.bungeecord status by using AuthMe built-in method bukkitService.isBungeeCordConfiguredForSpigot() and disable hook if it enabled and not behind an BungeeCord proxy.
Register plugin message channel without BungeeCord proxy will allow attacker send fake login payload to treat AuthMe login with Plugin Message for him and bypass the user login.
This commit also updated SettingsWarner for new behavior.
* If a player is not registered then we send a LOGIN plugin message on join
* Make looking up a profile optionally quiet
This prevents an issue where a forcedLogin of a player that doesn't exist occurring when an unregistered player switches a server. The first login would tell AuthBungee that the player is logged in, and subsequent switches would have AuthBungee send a performLogin back that would then send an unregistered player error message to the player.
Co-authored-by: bundabrg <bundabrg@grieve.com.au>
Co-authored-by: Gabriele C <sgdc3.mail@gmail.com>
* Use context aware groups
* Revert "Use context aware groups"
This reverts commit 5adc6ef7
* Keep luckperm contexts after authentication
* Code cleanup
* Code cleanup
* Fix nullpointer for context maps
* Code cleanup
* Use uuids for sqlite and postgresql
* Revert "Use uuids for sqlite and postgresql"
This reverts commit 05296e5f23bd4379a89647656f08432c718e6f9c.
* Cleanup imports
* Fix test
Co-authored-by: David Maes <david.maes@kbc.be>
When OP customize bukkit/spigot plugins directory location, SQLite file will still on default directory.
It will cause directory not found exception. Also let SQLite file not correct in the plugin directory.
Co-authored-by: Yuehu Lin <dev@fntsr.tw>
enhanced some translation
Chinese is a beautiful and complicated language.
the way last translator translate was to hard? i guess? just not friendly
i did some minor changes, now the language isn't so hard. and i also change the translation of 2fa. 两步验证 is cool. but 双重认证 is more accurate
plz aprove
HarvelsX