While using the ETX software, I noticed that users with identical usernames can log in successfully even if their passwords, home directories and shell paths are different. Only a matching username is required for login. My test‑case details are listed below:
1. The ETX server is integrated with LDAP. The LDAP user `user` has the password `password123`, home directory `/net_home` and shell path `/bin/csh`. There is also a local user with the same username `user` on the ETX node server, whose password is `password456`, home directory `/home` and shell path `/bin/bash`. Under this scenario, the user `user` is able to launch a virtual desktop successfully on the ETX node. And it picks up the home directory and shell variables from the local `user` account on the node, instead of the values from LDAP.
2. The ETX server uses Node A for account authentication, and Node B for virtual‑desktop loading. Node A and Node B both contain a user named `user`, but their passwords, home directories and shell paths are completely different. Even in this configuration, the user `user` can still launch the virtual desktop successfully on the ETX node. The session loads the home and shell variables from the local user on Node B, not from the authentication server (Node A).
Could you please clarify whether this behavior is a bug in the ETX authentication workflow, or an intentional feature designed for compatibility across different node servers?
