mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-01-01 03:37:05 -06:00
ad717bff3c
If the client installer fails for some reason and --force was not used then roll back the configuration. This is needed because we touch /etc/sysconfig/network early in the configuration and if it fails due to any number of issues (mostly related to authentication) it will not be reset. We may as well run through the entire uninstall process to be sure the system has been reset. https://fedorahosted.org/freeipa/ticket/1704 |
||
---|---|---|
.. | ||
firefox | ||
ipa-install | ||
ipaclient | ||
man | ||
AUTHORS | ||
config.c | ||
configure.ac | ||
ipa-client-common.c | ||
ipa-client-common.h | ||
ipa-client.spec.in | ||
ipa-getkeytab.c | ||
ipa-join.c | ||
ipa-rmkeytab.c | ||
Makefile.am | ||
NEWS | ||
README | ||
version.m4.in |
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.