Fix the ca certificate handling in the client sessions
The verify parameter is a 3 state parameter:
- it can be False if disabling CA checking is requested (insecure TLS)
- it can be set to True to check CA with the system CA bundle
- finally the path to the CA cert can be passed which must be used to
check the session
The cert parameter used currently is a client certificate, which is
obviously wrong in this case.
Change-Id: I100163713236a6096197e011963d08e994312dcd
Closes-Bug: #1593268
(cherry picked from commit 9d428206cd7326ffc29101745dc4a2b12461760f)
Reviewed: https:/ /review. openstack. org/334806 /git.openstack. org/cgit/ openstack/ sahara/ commit/ ?id=e46f0c77b7b b0167d48a9be915 ce5e028e44dca6
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit e46f0c77b7bb016 7d48a9be915ce5e 028e44dca6
Author: Gyorgy Szombathelyi <email address hidden>
Date: Thu Jun 16 17:01:35 2016 +0200
Fix the ca certificate handling in the client sessions
The verify parameter is a 3 state parameter:
- it can be False if disabling CA checking is requested (insecure TLS)
- it can be set to True to check CA with the system CA bundle
- finally the path to the CA cert can be passed which must be used to
check the session
The cert parameter used currently is a client certificate, which is
obviously wrong in this case.
Change-Id: I100163713236a6 096197e011963d0 8e994312dcd fc29101745dc4a2 b12461760f)
Closes-Bug: #1593268
(cherry picked from commit 9d428206cd7326f