Closed lekro closed 4 years ago
Correct, all users are required to have a group matching their username.
Currently, I'd classify this as a bug, because the only real issue is I don't know how to get nodejs/npm modules to report back to me what a user's primary group is (id -gn
).
This issue is fixed in pull request #293
Primary user group can be fetched with userid.gids(username)[0]
instead of userid.gid(username)
I am facing the same issue where I can't log in because my user doesn't have a matching group. I see that the PR is blocked. Can someone address this, please? Or, take the fix for groupname out of the LDAP related portions?
I've added the non-ldap portions of the code, which does indeed fix the issue of not having a matching group.
Creating a user "madeup" with group memberships including only "users" worked; successfully created a server.
Situation: I am running Ubuntu Server 16.04 and installed MineOS node via the instructions on the wiki. I have updated to a recent git commit following the instructions, but the issue persists.
I have multiple users, including myself, all with primary group
minecraft
with gid=1001. My uid is 1000. The WebUI appears as follows. The username in the top corner is not shown, and no servers are visible, even ones of which I am the owner.The following error appears in
/var/log/mineos.log
.I create a new (dummy) group with a (bogus) GID 9999, and don't add myself to it:
Now the WebUI loads fine and will show all servers I have made.
Adding a group with GID 1000 but different name causes the same issue:
Is this intended behavior? Are all users required to have a group with their username?
EDITS: run json through formatter