I'd really like us to avoid trying things at random here: from what is stated in comment #2 you propose to change the management endpoint of Keystone from HTTP to HTTPS, which *must not* be the case for the SSL configuration we have in MOS 8.0, which only applies to public endpoints.
At this point, this seems to be a purely Tempest problem to me. Heat and Keystone are configured and work as expected.
I'd really like us to avoid trying things at random here: from what is stated in comment #2 you propose to change the management endpoint of Keystone from HTTP to HTTPS, which *must not* be the case for the SSL configuration we have in MOS 8.0, which only applies to public endpoints.
At this point, this seems to be a purely Tempest problem to me. Heat and Keystone are configured and work as expected.