mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2025-02-25 18:55:28 -06:00
CRL migrate procedure did not check if a CA was actually configured on an updated master/replica. This caused ipa-upgradeconfig to crash on replicas without a CA. Make sure that CRL migrate procedure is not run when CA is not configured on given master. Also add few try..except clauses to make the procedure more robust. There is also a small refactoring of "<service> is not configured" log messages, so that they have matching log level and message. dogtag.py constants were updated to have a correct path to new CRL directory on Fedora 18 (dogtag 10). https://fedorahosted.org/freeipa/ticket/3159 |
||
---|---|---|
.tx | ||
checks | ||
contrib | ||
daemons | ||
doc | ||
init | ||
install | ||
ipa-client | ||
ipalib | ||
ipapython | ||
ipaserver | ||
selinux | ||
tests | ||
util | ||
.bzrignore | ||
.gitignore | ||
API.txt | ||
autogen.sh | ||
BUILD.txt | ||
Contributors.txt | ||
COPYING | ||
freeipa.spec.in | ||
ipa | ||
ipa-compliance.cron | ||
ipa.1 | ||
lite-server.py | ||
make-doc | ||
make-lint | ||
make-test | ||
make-testcert | ||
makeapi | ||
Makefile | ||
MANIFEST.in | ||
README | ||
setup-client.py | ||
setup.py | ||
TODO | ||
VERSION | ||
version.m4.in |
IPA Server What is it? ----------- For efficiency, compliance and risk mitigation, organizations need to centrally manage and correlate vital security information including: * Identity (machine, user, virtual machines, groups, authentication credentials) * Policy (configuration settings, access control information) * Audit (events, logs, analysis thereof) Since these are not new problems. there exist many approaches and products focused on addressing them. However, these tend to have the following weaknesses: * Focus on solving identity management across the enterprise has meant less focus on policy and audit. * Vendor focus on Web identity management problems has meant less well developed solutions for central management of the Linux and Unix world's vital security info. Organizations are forced to maintain a hodgepodge of internal and proprietary solutions at high TCO. * Proprietary security products don't easily provide access to the vital security information they collect or manage. This makes it difficult to synchronize and analyze effectively. The Latest Version ------------------ Details of the latest version can be found on the IPA server project page under <http://www.freeipa.org/>. Documentation ------------- The most up-to-date documentation can be found at <http://freeipa.org/page/Documentation/>. Quick Start ----------- To get started quickly, start here: <https://fedorahosted.org/freeipa/wiki/QuickStartGuide> Licensing --------- Please see the file called COPYING. Contacts -------- * If you want to be informed about new code releases, bug fixes, security fixes, general news and information about the IPA server subscribe to the freeipa-announce mailing list at <https://www.redhat.com/mailman/listinfo/freeipa-interest/>. * If you have a bug report please submit it at: <https://bugzilla.redhat.com> * If you want to participate in actively developing IPA please subscribe to the freeipa-devel mailing list at <https://www.redhat.com/mailman/listinfo/freeipa-devel/> or join us in IRC at irc://irc.freenode.net/freeipa