Today the Azure deployment feature is configured statically with a username and password for the virtual machine (VM) that it creates upon solution deployment. This means that every single VM uses the same credentials. Even users who bring different Azure credentials (different payment accounts) will be given VMs with the same credentials.
Repair the deployment UI and the back-end to accept these credentials from the user at each deployment, instead of using statically configured information.
Originally I classified this as a bug due to security concerns of shared credentials. The existing situation is extremely difficult to defend.
Ken Kristiansen changed this to a user story,.
|3643,2||Add code for new credential of vm||master||acumos-azure-client||Status: MERGED||+2||+1|
|3656,1||Update code for cds 2.0.2 and notification changes||master||acumos-azure-client||Status: MERGED||+2||+1|
|3662,1||Updated cds 2.0.3 and notification||master||acumos-azure-client||Status: MERGED||+2||+1|