Thanks for the feedback. I agree that the names are hard to follow, they can change to something more intuitive. Or we can even provide a tooltip for more information.
As for the look and feel, I don't agree that its easier if all the options are listed. Image if you had 5 different ways for users to log in and they are all shown at once. That's a lot to take in.
This approach keep things simply, it's really not that hard to pick from a list.
I'm just building on top of the visuals we already have without changing things too drastically. If you have a better idea, I would love to see it.
-----Ioram Schechtman Sette <i...@cin.ufpe.br> wrote: -----
To: "OpenStack Development Mailing List (not for usage questions)" <email@example.com>
From: Ioram Schechtman Sette <i...@cin.ufpe.br>
Date: 02/05/2015 03:15AM
Subject: Re: [openstack-dev] [horizon][keystone]
I agree with Anton that the names are not intuitive for users.
I would use something like:
- Local authentication (for local credentials)
- ?? (I also have no idea of what is a Default protocol)
- Authenticate using <name of IdPs or federation> (something which is easy to the user understand that he could use or not - this is for the discovery service or remote IdP)
Here in the University of Kent we used another approach.
Instead of selecting the method using a "list/combo" box, we present all the options in a single screen.
I think it's not beautiful, but functional.
I think it would be easier to the user if they could have all the options in a single interface, since it doesn't become too much loaded (visually polluted).
OpenStack Development Mailing List (not for usage questions)