You are prompted for a password, but even if you would provide correct password, you would not be granted access. This is how this option works.
It is another level of secrecy, that the server is not leaking the list of users that have valid account. If it would not do that, attacker could scan the server for valid users in minutes and attack only the existing users, which he can expect to have weak password or whatever else guess.
The key in the user database, /etc/passwd or something else, is the login name: that’s all that you provide to identify yourself when you log in. From that key, a program can retrieve all the other information stored in the user database; this happens with no regard for any other user in the user database, even other users with the same user id. (Typically, this is done with getpwnam or getpwnam_r, either directly or via PAM.)
Thus the login name leads to the stored password, the user id, the (primary) group id, the GECOS information, the home directory and shell. This means that two users can share the same user id, yet have different home directories and shells! (This was commonly used in the past to provide a fall-back, statically-linked shell for root; you’d have the usual root user with id 0 and shell /bin/bash or whatever, and another user, say sashroot, with id 0 and a different shell.)
Hence the answer to
does the group ID field depend on user name or on user ID?
is that it depends only on the user name.
The key in the group database is also the group name. From that key, a program can retrieve all the other information stored in the group database; again this happens with no regard for any other group in the group database. (When determining a user’s secondary groups, the process is more complex than reading the user database: there is no function to list groups to which a given user belongs, so this is typically done in a loop involving getgrent and endgrent.)
Thus the group name leads to the group password, group id, and the list of group members, which is a list of user names. To build a user’s set of secondary groups, all the groups are enumerated, and the user’s login name is matched against the group’s members. So not only can two different users with the same user id have different primary groups, they can belong to a different set of secondary groups!
Hence the answer to
In other words, can different usernames for the same user ID have different group IDs, or must all the usernames for the same user ID have the same group ID?
is that a user’s groups only depend on the user name, and different user names can share a user id yet have different primary and secondary groups.
Best Answer
Good way for nice output of /etc/passwd file:
Now you can sort it:
With groups names in last column (no parenthesis):