[CLOUDSTACK-7468] NetScaler SSL Termination does not handle Projects as expected

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.5.0, 4.4.1
• Fix Version/s: 4.5.0, 4.4.1
• Component/s: Network Devices
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Will Stevens
• Reporter: Will Stevens
• Created: 02/Sep/14 15:00
• Updated: 04/Sep/14 18:21
• Resolved: 04/Sep/14 18:21

Description

Currently the 'uploadSslCert' api call does not take any details about who should own the SSL Cert. It basically assigns the cert to the caller and thats it.

This breaks the expected behavior for projects and also does not allow for an admin to upload certificates on behalf of one of their users.

This fix should not adjust the database entities at all, but should allow the API calls to handle the additional cases.

The following changes should be made:

• If 'uploadSslCert' is called without any account details, it should behave how it does now and assign the cert to the caller.
• If 'uploadSslCert' includes option 'account' and 'domainId' fields, the uploaded cert will be applied to that account.
• If 'uploadSslCert' includes a 'projectId', then the cert is applied to that project.
• The 'listSslCerts' api should also take an optional 'projectid' field to list the ssl certs associated with that project.
• The api response for both 'uploadSslCert' and 'listSslCerts' should be updated to include additional information about the account or project as well as the domain in which the cert is assigned.