IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-29 10:21:18 -06:00
Code Issues Packages Projects Releases Wiki Activity
ee84c6ae78
freeipa/ipa-client
History
Jan Cholasta 81729e22d3 vault: Move vaults to cn=vaults,cn=kra 
https://fedorahosted.org/freeipa/ticket/3872

Reviewed-By: David Kupka <dkupka@redhat.com>
2015-06-10 16:17:34 +00:00
..
ipa-install Clarify host name output in ipa-client-install 2015-06-05 19:25:56 +02:00
ipaclient ipa client: make --ntp-server option multivalued 2015-04-24 15:36:07 +02:00
man vault: Move vaults to cn=vaults,cn=kra 2015-06-10 16:17:34 +00:00
AUTHORS
config.c Fix coverity issues in client CLI tools 2011-11-23 00:30:41 -05:00
configure.ac Use asn1c helpers to encode/decode the getkeytab control 2014-11-20 10:52:13 -05:00
ipa-client-common.c ipa-client: Use "ipa" as the package name for i18n 2013-07-19 12:26:28 +02: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 Use asn1c helpers to encode/decode the getkeytab control 2014-11-20 10:52:13 -05:00
ipa-join.c Fix unchecked return value in ipa-join 2014-11-25 08:23:24 +00:00
ipa-rmkeytab.c Typos in ipa-rmkeytab options help and man page 2015-02-10 08:30:46 +01:00
Makefile.am Remove usage of app_PYTHON in ipaserver Makefiles 2014-12-10 15:42:39 +01:00
NEWS
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.