Description of problem: rerunning packstack will generate a new ssl file for horizon i did this first sed -i 's/CONFIG_HORIZON_SSL=n/CONFIG_HORIZON_SSL=y/g' packstack.answer then ran packstack i then logged into the horizon dashboard and accepted the ssl file later i decided to enable the demo user and add in the cirros image so i modifed the answer file and re ran packstack i then logged into the horizon dashboard and accepted the _NEW_ ssl file so thinking ahead one year from now, we _will_ need to generate a new ssl file so maybe a config option like "generate new ssl file for horizon =y" should be included ? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Packstack generates self signed SSL certificates, this certificates are just for testing and they are not suppoused to be used in production. If you need a long term certificate you should get a verified certficate from verisign or create your CA and sign your certificates. And then add them to packstack answer file.