Alfredo Moralejo e40e6d934b Fix ipv6 certificate to make it compliant with IDNA
Currently we are setting "DNS.0 = ::1", but ::1 is not a valid
A-Label for IDNA so the certificate is not correct.

Additionally, we are setting wrong value for DNS.0 = 127.0.0.1
in the ipv4 certificate.

Finally, removing issuerAltName from both ipv4 and ipv6 certificates
as they are not needed for the jobs.

New versions of python-cryptography are more strict to check
certificates content and does not allow to have not compliant
DNS names so we need to fix the certificate to bump python-cryptography.

Note that horizont tempest plugin does not support ipaddress SANs based
certificate validation so I'm disablint certificate validation for
dashboard in this patch.

Depends-On: Iea7a4b85ac64572fac0f0ad871649a79fbc1c0f5

Change-Id: Ib519d222e07e26d3683b24359e2f67728cdd8029
2018-03-20 22:38:03 +01:00
..
2018-01-09 17:23:05 +00:00
2017-09-15 09:10:25 -04:00
2018-02-05 09:24:14 +05:30
2017-09-15 09:10:25 -04:00
2018-02-20 18:29:56 +05:30
2017-12-22 19:03:12 +00:00
2017-09-15 09:10:25 -04:00
2016-04-01 20:32:35 -04:00
2017-09-15 09:10:25 -04:00