11.3 breaks connecting to existing shared project if local username differs from remote username

[Montg0mery]

Describe the bug
With 11.3, opening an existing shared project (which is shared using a Ghidra server) now has the username field in the login prompt as non-editable, and pre-filled in with the local Linux username, which in my case, is not the same as my username on the server / network (which is setup with LDAP authentication).

In 11.2, everything worked fine. The username field in the login prompt was editable, and the first time you connected to the server, you typed your server / network username, and then every time after that, the network username was remembered from before and pre-filled correctly.

Environment (please complete the following information):

• OS: Linux
• Java Version: 21.06
• Ghidra Version: 11.3
• Ghidra Origin: official GitHub release

This significantly breaks connecting to the server to work on shared projects.

[ab9rf]

I was able to work around this issue by adding VMARGS=-Duser.name=<username> (where <username> matches the name used on the Ghidra server) to support/launch.properties; however, I also had to manually edit the project.prp of all local projects to reflect this changed username.

This is obviously less than ideal, and is clearly not an option for people who connect to more than one server each using a different username.

[ab9rf]

Also, the regression in behavior is due to the changes in 867fdea

[electricworry]

Yep, same issue for me. Still using Ghidra Server 11.1.2, but on update to Client 11.3 the username is now a label not a mutable field.

[ghidra1]

Sorry about this regression. A fix is in the works and hope to get a patch release out quickly.