On 4.6.2014 09:55, Petr Vobornik wrote:
On 4.6.2014 09:37, Petr Spacek wrote:
On 4.6.2014 08:44, Martin Kosek wrote:
On 06/04/2014 08:34 AM, Martin Kosek wrote:
This is really good proposal! Scroll down to see three nit picks:
- Host groups
- OTP Tokens
- Password Policy
- Kerberos Ticket Policy
- SELinux User Maps
Alternatively, we could rename Policy to "Authorization" as both HBAC and
SELinux is about authorizing what an authenticated user can do. We
need to move Automember to different place, though this one is
difficult - it
relates both to Users and Hosts, just like Netgroup.
- Trust configuration
- (future) Views
^^^ I would like to see this under "Authentication". Nowaways it is used
to authenticate machines and it will be extended to user authentication
as soon as Smart Card support is added.
- (future) Replication topology
^^^ Personally, I would place it under "IPA Configuration".
- (future) Vault
^^^ Why is Vault under "Infrastructure"? It sounds like "Authentication"
to me. It is meant to store plain-text passwords etc., no?
It seems that I'm proposing to reduce "Infrastructure" to "DNS". We can
move DNS somewhere or make DNS top-level item until we get DHCP or
I would rather avoid having a temporary top-level item.
Temporary ~ years in this case. Is it good enough? :-)
I personally don't like categories with one item in them, it seems ridiculous.
Look at "Time" menu in OrangeHRM :-) You have to go through it just to click
to the only option inside. Ridiculous.
My point is that distinction between "Infrastructure" and "IPA server" or it's
configuration is really vague. I'm worried that people (or at least I) will
always look in the "wrong" category first which makes me unhappy.
This also opens the question if DNS management is really the right
business for us :-) I'm personally not sure :-)
^^^ Can it be "IPA configuration" or something like that? Just
"Configuration" seems too vague to me. After all, everything in the UI
is some kind of configuration :-)
We can leave the old "IPA Server" name. I agree that "Replication topology"
could be here because it configures the tool and not the data, similar to
other items under this category. But I think that many users would try to find
it in infrastructure.
BTW can we clarify somehow that this applies purely to IPA? Maybe "IPA Server"
category will make it clear enough...
- Access Control (RBAC)
- Realm Domains
- ID Ranges
Freeipa-devel mailing list