freeipa/ipa-client
Rob Crittenden 4f37775db7 Use a more specific name for the IPA server certificate we install.
This should avoid conflicts with any other certs that might be installed
there.

ticket 49
2010-09-17 17:21:43 -04:00
..
firefox Set the license uniformly to GPLv2 only. 2008-02-04 15:15:52 -05:00
ipa-install Use a more specific name for the IPA server certificate we install. 2010-09-17 17:21:43 -04:00
ipaclient Better LDAP error handling in ipa-client-install 2009-12-01 09:52:14 -07:00
man Fix certmonger errors when doing a client or server uninstall. 2010-09-09 16:38:52 -04:00
AUTHORS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
config.c Fix a crash and memory leak in get_config_entry() 2010-02-16 10:42:45 -05:00
configure.ac Drop --with-openldap option in the client. This is no longer optional. 2010-06-21 09:52: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 ldap_initialize 2010-08-20 09:47:54 -04:00
ipa-join.c const correctness 2010-08-20 09:47:42 -04:00
ipa-rmkeytab.c Add the popt auto-help/usage macro for enhanced help output. 2010-03-02 18:20:13 -05:00
Makefile.am A utility for removing principals from a keytab. 2009-12-04 16:29:09 -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.