I’m an object oriented kind of developer. I likes a strong domain model, a clear separation of responsibility, and all of the goodness that makes code clean. Why, then, am I so resistant to introducing a domain model into the FreeIPA WebUI?
The FreeIPA Project (http://freeipa.org) is proud to present FreeIPA
version 2.0.
FreeIPA is an integrated security information management solution
combining Linux (Fedora), 389 Directory Server, MIT Kerberos and NTP.
FreeIPA binds together a number of technologies and adds a web interface
and command-line administration tools.
The FreeIPA UI approach attempts to use a Domain Specific languages for UI definition. While I like how it has emerged thus far, I don’t feel we are yet where we need it to be.
Having worked on the FreeIPA GUI from inception through GA (well, RC3, soon to be GA) here’s what I’ve learned about the writing a web application using today’s technologies.
Reposted from the FreeIPA devel list.
To all freeipa-interest, freeipa-users and freeipa-devel list members,
The FreeIPA project team is pleased to announce the availability of the Release Candidate 3 release of freeIPA 2.0 server [1]. This should be the last release candidate, becoming the final release if no critical problems are found.
P is for Policy. One aspect of policy management that has the potential to be the killer feature is centralized SUDO.