You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/09/19 10:11:53 UTC
[jira] [Updated] (CLOUDSTACK-2024) cloudstack-setup-management with
https not works (incorrect path and missing keystore file)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhinandan Prateek updated CLOUDSTACK-2024:
-------------------------------------------
Fix Version/s: (was: 4.2.0)
4.2.1
> cloudstack-setup-management with https not works (incorrect path and missing keystore file)
> -------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2024
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2024
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Install and Setup
> Affects Versions: 4.1.0, 4.2.0
> Environment: CentOS 6.4
> Reporter: Milamber
> Assignee: Milamber
> Fix For: 4.2.1
>
>
> when you execute (if I understood well) /usr/bin/cloudstack-setup-management --https
> we setup a tomcat with HTTPS.
> This doesn't works.
> In the file :
> /etc/cloudstack/management/server-ssl.xml
> There is this ligne:
> keystoreFile="/etc/cloud/management/cloudmanagementserver.keystore"
> should be replace by
> keystoreFile="/etc/cloudstack/management/cloudmanagementserver.keystore"
>
> but the file cloudmanagementserver.keystore dosen't exist here
> it lives : /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/cloud.keystore
> (Not sure it's the good keystore, it contain one key:
> mykey, Apr 9, 2013, PrivateKeyEntry,
> Certificate fingerprint (MD5): 69:0A:F3:60:F8:6B:65:AD:50:E5:63:63:00:9B:0D:68)
> The questions (to Hugo) :
> make a symbolic link ? or a copy ? in the cloudstack-setup-management script.
> or create a new self-sign certificate.
> Note: Perhaps the same issue with Ubuntu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira