© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I suspect part of the reason why this has not been implemented yet is because the service_type names are hardcoded in the keystone charm [1] whereas they are in fact needed in each charm that implements a keystone_authtoken section which comes via charmhelpers. So one way to fix this would be to move [1] into [2] and use that when generating contexts to render the authtoken section templates.
[1] https:/
[2] https:/