IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-24 16:10:02 -06:00
Code Issues Packages Projects Releases Wiki Activity
828c9b9cdd
freeipa/ipa-client
History
Martin Nagy 828c9b9cdd Delete old mercurial files.
2008-08-15 08:54:37 +02:00
..
firefox Set the license uniformly to GPLv2 only. 2008-02-04 15:15:52 -05:00
ipa-install Wrap up the raw_input() to user_input() for convenience and uniformity. 2008-07-23 10:05:06 -04:00
ipaclient Handle exceptions more gracefully on systems with python-ldap 2.2.0 2008-04-14 18:23:29 -04:00
man Fix some minor man page issues. 2008-06-04 12:50:13 -04: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 Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -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 some small issues that caused compiler warnings, like uninitialized or unused variables or missing krb5 prototypes. 2008-06-30 14:17:10 -04:00
Makefile.am Fix versioning for configure.ac and ipa-python/setup.py 2008-08-11 18:31:05 -04: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

README 

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.