> now broken after configuring a federation protocol
>
> - clouds.yaml / openrc in Horizon
horizon provides a way for operators to customize their own clouds.yaml and openrc (tracked by bug 1795851).
Doesn't it work?
If someone would like to move this forward more, we (as horizon developers) need an example of the token auth response of /v3/auth/tokens for non-password case (like federation) [1]. An example like comment #7 above is not sufficient because we cannot know how we organize openrc/clouds.yaml information. [2] is an example response for a simple password auth.
> now broken after configuring a federation protocol
>
> - clouds.yaml / openrc in Horizon
horizon provides a way for operators to customize their own clouds.yaml and openrc (tracked by bug 1795851).
Doesn't it work?
If someone would like to move this forward more, we (as horizon developers) need an example of the token auth response of /v3/auth/tokens for non-password case (like federation) [1]. An example like comment #7 above is not sufficient because we cannot know how we organize openrc/clouds.yaml information. [2] is an example response for a simple password auth.
[1] https:/ /docs.openstack .org/api- ref/identity/ v3/index. html?expanded= validate- and-show- information- for-token- detail, password- authentication- with-unscoped- authorization- detail# password- authentication- with-unscoped- authorization paste.openstack .org/show/ 787351/
[2] http://