4) Even when using CoronaActivation.txt, you can delete the file after initial activation - the login will then be stored in breakable, but encrypted form (same as #3), and automatic extensions of the license will work
That's something I didn't know. Good that this information got added to the helpdesk article. Already fixes most of the problems. So the only place where unencrypted information is stored is the lic server. It's my personal opinion but I find it a good habit to store data like that encrypted, I also don't know any other license server application which does it any way else (which doesn't mean there aren't any).
My suggestion would be to just add a way to add credentials via the licserver and 2 textboxes, info gets stored encrypted, no manual .txt file generation necessary.
Combined with a way to manage multiple user accounts and information about used lics it's all fine