mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-01-13 09:41:55 -06:00
f352702d67
This new extended operation is tried by default and then the code falls back to the old method if it fails. The new method allows for server side password generation as well as retrieval of existing credentials w/o causing regeneration of keys on the server. Resolves: https://fedorahosted.org/freeipa/ticket/3859 Reviewed-By: Nathaniel McCallum <npmccallum@redhat.com> |
||
|---|---|---|
| .. | ||
| 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.