Go to file
Rob Crittenden ca07cdb390 Add detection to the update tool to detect when it would apply changes.
Remove SUP name from RFC2307bis.update to match FDS
2008-09-19 18:04:40 -04:00
contrib/RHEL4 Now that admin is in the common users tree make the nss_ldap 2008-05-29 09:43:08 -04:00
ipa-admintools Remove reference to very unlikely service examples that are not 2008-09-18 17:23:12 -04:00
ipa-client We were assuming that, if the realm was correct then also the 2008-09-18 17:23:12 -04:00
ipa-python Don't try to discover servers if we specified them on command line. 2008-09-17 23:06:23 +02:00
ipa-radius-admintools Rework config.py and change cli tools. Maintain order of IPA servers from command line, config and DNS. Parse options before detecting IPA configuration. Don't ignore rest of the options if one is missing in ipa.conf. Drop the --usage options, we will rely on --help. Fixes: 458869, 459070, 458980, 459234 2008-09-11 23:34:01 +02:00
ipa-radius-server Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00
ipa-server Add detection to the update tool to detect when it would apply changes. 2008-09-19 18:04:40 -04:00
LICENSE Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
Makefile apparently the "configure" target is never used 2008-08-13 15:57:28 -04:00
README Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
VERSION Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00

                               IPA Server

  What is it?
  -----------

  For efficiency, compliance and risk mitigation, organizations need to
  centrally manage and correlate vital security information including:

    * Identity (machine, user, virtual machines, groups, authentication
      credentials)
    * Policy (configuration settings, access control information)
    * Audit (events, logs, analysis thereof) 

  Since these are not new problems. there exist many approaches and
  products focused on addressing them. However, these tend to have the
  following weaknesses:

    * Focus on solving identity management across the enterprise has meant
      less focus on policy and audit.
    * Vendor focus on Web identity management problems has meant less well
      developed solutions for central management of the Linux and Unix
      world's vital security info. Organizations are forced to maintain
      a hodgepodge of internal and proprietary solutions at high TCO.
    * Proprietary security products don't easily provide access to the
      vital security information they collect or manage. This makes it
      difficult to synchronize and analyze effectively. 

  The Latest Version
  ------------------

  Details of the latest version can be found on the IPA server project
  page under <http://www.freeipa.org/>.

  Documentation
  -------------

  The most up-to-date documentation can be found at
  <http://freeipa.org/page/Documentation/>.

  Licensing
  ---------

  Please see the file called LICENSE.

  Contacts
  --------

     * If you want to be informed about new code releases, bug fixes,
       security fixes, general news and information about the IPA server
       subscribe to the freeipa-announce mailing list at
       <https://www.redhat.com/mailman/listinfo/freeipa-interest/>.

     * If you have a bug report please submit it at:
       <https://bugzilla.redhat.com>

     * If you want to participate in actively developing IPA please
       subscribe to the freeipa-devel mailing list at
       <https://www.redhat.com/mailman/listinfo/freeipa-devel/> or join
       us in IRC at irc://irc.freenode.net/freeipa