freeipa/ipa-client
2008-01-23 10:30:18 -05:00
..
firefox Autotool ipa-client - patch from William Jon McCann <mccann@jhu.edu> 0001-01-01 00:00:00 +00:00
ipa-install Fix issues reported by rpmlint. 2008-01-18 16:20:36 -05:00
ipaclient Fix issues reported by rpmlint. 2008-01-18 16:20:36 -05:00
.hgignore Autotool ipa-client - patch from William Jon McCann <mccann@jhu.edu> 0001-01-01 00:00:00 +00:00
AUTHORS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
autogen.sh Correct PACKAGE in ipa-client/autogen.sh. 0001-01-01 00:00:00 +00:00
configure.ac Merge version changes with upstream 2007-12-21 11:53:31 -05:00
ipa-client.spec Fix issues reported by rpmlint. 2008-01-18 16:20:36 -05:00
ipa-client.spec.in Fix issues reported by rpmlint. 2008-01-18 16:20:36 -05:00
ipa-getkeytab.c Big changeset that includes the work around keytab management. 2007-12-21 11:37:19 -05:00
Makefile.am Update the .spec filenames in EXTRA_DIST 2008-01-11 10:36:25 +00: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

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.