IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2024-12-28 18:01:23 -06:00
Code Issues Packages Projects Releases Wiki Activity
68825e7ac6
freeipa/ipa-client
History
Jan Cholasta 608851d3f8 Check LDAP instead of local configuration to see if IPA CA is enabled 
The check is done using a new hidden command ca_is_enabled.

https://fedorahosted.org/freeipa/ticket/4621

Reviewed-By: David Kupka <dkupka@redhat.com>
2014-10-17 12:53:11 +02:00
..
ipa-install Check LDAP instead of local configuration to see if IPA CA is enabled 2014-10-17 12:53:11 +02:00
ipaclient Check LDAP instead of local configuration to see if IPA CA is enabled 2014-10-17 12:53:11 +02:00
man Add ipa-client-install switch --request-cert to request cert for the host 2014-10-16 19:11:52 +02:00
AUTHORS Fix build from autoconf patch import. 0001-01-01 00:00:00 +00:00
config.c Fix coverity issues in client CLI tools 2011-11-23 00:30:41 -05:00
configure.ac Enable building in C99 mode 2014-02-14 16:03:24 +01: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 Fix ipa-getkeytab for pre-4.0 servers 2014-07-25 08:22:46 +02:00
ipa-join.c Add support for re-enrolling hosts using keytab 2013-03-12 15:13:09 +01:00
ipa-rmkeytab.c Use indexed format specifiers in i18n strings 2012-04-10 18:07:10 -04:00
Makefile.am Remove CFLAGS duplication. 2013-12-06 14:44:41 +01: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.