2ffcf18d00
Related-bug: 1409142 As part of the fix for the related bug - we've added protocol checking to mitigate MITM attacks, however we base protocol checking on a config option that is normally only intended for compute hosts. This is quite user hostile, as it is now important that all nodes running compute and proxy services have this option in sync. We can do better than that - we can persist the URL the client is expected to use, and once we get it back on token validation, we can make sure that the request is using the intended protocol, mitigating the MITM injected script attacks. This patch makes sure that the access_url is persisted with the token - the follow-up patch makes consoles use that info. Change-Id: I02a377f54de46536ca35413b615d3298967afc33 |
||
---|---|---|
.. | ||
monitors | ||
resources | ||
__init__.py | ||
api.py | ||
arch.py | ||
build_results.py | ||
cells_api.py | ||
claims.py | ||
cpumodel.py | ||
flavors.py | ||
hv_type.py | ||
instance_actions.py | ||
manager.py | ||
power_state.py | ||
resource_tracker.py | ||
rpcapi.py | ||
stats.py | ||
task_states.py | ||
utils.py | ||
vm_mode.py | ||
vm_states.py |