Store the key of foreign server in the address book

I have a private server, with about 90 machines. I also need to connect to machines that are managed by my work's Rustdesk system. I can do this using the format 1234@work.server?key=secretkey

However, when I add this to my address book, it doesn't keep the key part, only the number and server name. This means I have to edit the connection for each time I want to connect, and this is painful, many times a day.

I think the desktop application, and therefore server, should keep and store the key if specified.

If you want to get fancy, you could have an option to store the key for a foreign server somewhere else, such that 1234@work.server would look up the work.server name and find the key. This would then mean I didn't have to add the key for all of the machines.

Another option would be to switch servers for the desktop app, but that would seem much more work!

Thanks, Matthew

The issue names no files or tests; begin by tracing how the desktop address book parses and persists server addresses, then follow how connections use the stored address. Done means a saved foreign-server address retains its key and can reconnect without manual editing, with the chosen storage behavior documented or covered by tests.