You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Will Stevens (JIRA)" <ji...@apache.org> on 2014/09/02 17:00:22 UTC

[jira] [Created] (CLOUDSTACK-7468) NetScaler SSL Termination does not handle Projects as expected

Will Stevens created CLOUDSTACK-7468:
----------------------------------------

             Summary: NetScaler SSL Termination does not handle Projects as expected
                 Key: CLOUDSTACK-7468
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7468
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Devices
    Affects Versions: 4.5.0, 4.4.1
            Reporter: Will Stevens
            Assignee: Will Stevens


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)