freeipa/ipa-client
Ondrej Hamada bf57388e54 Client install root privileges check
ipa-client-install was failing and returning traceback when
wasn't run by root. It was caused by logging initialization that
was taking part before the root privileges check. To correct it,
the check was moved before the logging initialization.

https://fedorahosted.org/freeipa/ticket/2123
2011-11-21 09:39:37 +01:00
..
firefox Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-install Client install root privileges check 2011-11-21 09:39:37 +01:00
ipaclient ipa-client-install hangs if the discovered server is unresponsive 2011-10-12 00:50:22 -04:00
man Fix ipa-client-install -U option alignment 2011-10-14 10:35:15 +02:00
AUTHORS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
config.c Fix issues found by Coverity. 2011-05-09 16:23:40 -04:00
configure.ac Add configure check for libintl.h 2011-11-16 18:35:19 -05:00
ipa-client-common.c Change FreeIPA license to GPLv3+ 2010-12-20 17:19:53 -05:00
ipa-client-common.h include <stdint.h> for uintptr_t 2011-09-22 09:42:11 -04:00
ipa-client.spec.in Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00
ipa-getkeytab.c Fix build warnings 2011-08-26 08:24:48 -04:00
ipa-join.c Make ipa-join work against an LDAP server that disallows anon binds 2011-10-11 18:26:29 -04:00
ipa-rmkeytab.c Bad return values for ipa-rmkeytab command 2011-05-03 15:19:07 +02:00
Makefile.am Add configure check for libintl.h 2011-11-16 18:35:19 -05:00
NEWS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
README Add a copy of the LICENSE and populate some README's 2008-01-23 10:30:18 -05:00
version.m4.in Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04:00

Code to be installed on any client that wants to be in an IPA domain.

Mostly consists of a tool for Linux systems that will help configure the
client so it will work properly in a kerberized environment.

It also includes several ways to configure Firefox to do single sign-on.

The two methods on the client side are:

1. globalsetup.sh. This modifies the global Firefox installation so that
   any profiles created will be pre-configured.

2. usersetup.sh. This will update a user's existing profile.

The downside of #1 is that an rpm -V will return a failure. It will also
need to be run with every update of Firefox.

One a profile contains the proper preferences it will be unaffected by
upgrades to Firefox. 

The downside of #2 is that every user would need to run this each time they
create a new profile.

There is a third, server-side method. See ipa-server/README for details.