What horizon can know are limited to information included in token response. Horizon cannot know all required information to cover all possible authentication mechanism. From this reason, I think what horizon can support is only the basic password authentication.
Possible workaround is to provide a way to disable download links of openrc and clouds.yaml. When an operator uses a different auth method, they can disable the links.
Another possible solution is to provider a way to define a custom template for "openrc".
What horizon can know are limited to information included in token response. Horizon cannot know all required information to cover all possible authentication mechanism. From this reason, I think what horizon can support is only the basic password authentication.
Possible workaround is to provide a way to disable download links of openrc and clouds.yaml. When an operator uses a different auth method, they can disable the links.
Another possible solution is to provider a way to define a custom template for "openrc".
Does it sound reasonable?