Download this pastebin to your scripts directory (/usr/games/minecraft), giving it a name of whatever, like password_test.js (doesn’t really matter). We put it here so it can use the already-downloaded node.js modules.
Update the username and password to known-working combinations and then run it.
This is a minimal, self-contained snippet of code. It will cycle through the 3 available authentication methods MineOS uses. It doesn’t actually interact with MineOS in any way, so it should be able to tell us more swiftly what the issue is.
Keep in mind, I fully expect it to return 3 failures here–the only difference is that you won’t have to log into the webui to find it out.
Here’s an example of what it might output:
testing etc_shadow
expected value: mc
returned value: mc
testing posix
expected value: mc
returned value: true
testing pam
expected value: mc
returned value: true
The thing is: CentOS is often more locked-down than other distros, so it could be something like SELinux causing trouble, or PAM is more locked down, or …I don’t even know.
But the thing is, we have to systematically change Linux itself, then run this, until we get a working result. If, for example, PAM was not installed, disabled, or otherwise locked down, turning it on might make this program return a positive result. At that exact moment, we’d expect MineOS to work as well.
Of course, we could also expect test-auth.js to suddenly work when one of the components work, but this at least gives us individual feedback about which one (or ones) could be used based on your changes.